Triple
T6788924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hijra to Abyssinia |
E155882
|
entity |
| Predicate | hostRuler |
P60012
|
FINISHED |
| Object | Christian king of Aksum |
—
|
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: Christian king of Aksum | Statement: [Hijra to Abyssinia, hostRuler, Christian king of Aksum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostRuler Context triple: [Hijra to Abyssinia, hostRuler, Christian king of Aksum]
-
A.
hostNationRuler
Indicates that one entity serves as the ruling authority or leader of the nation in which the other entity is located or hosted.
-
B.
hostCourtRuler
chosen
Indicates that one entity serves as the ruling authority of the court hosted or held by another entity.
-
C.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
-
D.
currentRuler
Indicates that one entity is the present reigning ruler or head of state of another entity (such as a country, region, or polity).
-
E.
mainRuler
Indicates that one entity is the primary sovereign or highest-ranking ruler over another entity, such as a territory, people, or political unit.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2aa2e0c8190b994261826ae001d |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.