Triple
T38546078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Takhts of Sikhism |
E924966
|
entity |
| Predicate | hasCentralTakht |
P190891
|
FINISHED |
| Object | Akal Takht |
—
|
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: Akal Takht | Statement: [Five Takhts of Sikhism, hasCentralTakht, Akal Takht]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralTakht Context triple: [Five Takhts of Sikhism, hasCentralTakht, Akal Takht]
-
A.
takhtOf
chosen
Indicates a relationship where one entity serves as the throne, seat of authority, or ruling seat associated with another entity.
-
B.
ancestralSeatOf
Indicates that one entity is the traditional or original home, origin place, or foundational location associated with the lineage, heritage, or authority of another entity.
-
C.
hasPhysicalThrone
Indicates that an entity possesses or is associated with a tangible, physical throne as an object.
-
D.
centralCeremonyLocation
Indicates the place that serves as the primary or focal site where a ceremony is held.
-
E.
isDiplomaticCenterOf
Indicates that a location serves as the primary site or hub for conducting diplomatic activities and relations for a specified 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 3, 2026, 4:32 p.m.