Triple
T35027196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ila Orangun |
E1010370
|
entity |
| Predicate | clanOrKingdom |
P182021
|
FINISHED |
| Object | Ila Orangun kingdom |
—
|
NE NERFINISHED |
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: Ila Orangun kingdom | Statement: [Ila Orangun, clanOrKingdom, Ila Orangun kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanOrKingdom Context triple: [Ila Orangun, clanOrKingdom, Ila Orangun kingdom]
-
A.
clanType
Indicates the specific category or classification of a clan within a broader clan system or hierarchy.
-
B.
clientKingdomOf
Indicates a relationship where one kingdom is politically subordinate or tributary to another, more powerful kingdom while retaining limited internal autonomy.
-
C.
notableClans
Indicates that there exists a significant or historically important clan associated with the subject.
-
D.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
-
E.
clanDistrict
Indicates that a clan is associated with, based in, or traditionally linked to a particular district.
- F. None of above. chosen
Provenance (4 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.