Triple
T18867599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land of Punt |
E461479
|
entity |
| Predicate | hadRulers |
P8531
|
FINISHED |
| Object | local chiefs |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: local chiefs | Statement: [Land of Punt, hadRulers, local chiefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRulers Context triple: [Land of Punt, hadRulers, local chiefs]
-
A.
historicalRulers
chosen
Indicates that one entity has served as a ruler or governing authority over the other entity at some point in history.
-
B.
recognizedAsRulersBy
Indicates that certain entities are acknowledged or accepted by others as their legitimate rulers or authorities.
-
C.
coRulership
Indicates a relationship in which two or more entities share authority or power to rule jointly over the same domain or group.
-
D.
deFactoRulersDuringReign
Indicates that the referenced entities were the actual, effective rulers exercising power during the nominal reign of another ruler.
-
E.
hasNumberOfRulers
Indicates the quantity of rulers associated with or governing a given entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a6d1d081909b6dab2a5166a317 |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.