Triple
T9694226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pillan |
E234606
|
entity |
| Predicate | relationToAncestors |
P89662
|
FINISHED |
| Object | embodiment of ancestral spirits |
—
|
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: embodiment of ancestral spirits | Statement: [Pillan, relationToAncestors, embodiment of ancestral spirits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToAncestors Context triple: [Pillan, relationToAncestors, embodiment of ancestral spirits]
-
A.
hasGenealogicalRelation
Indicates that there exists a family or ancestry-based relationship (such as parent, child, sibling, or more distant kinship) between the related entities.
-
B.
relationToCreation
Indicates the nature of a connection or involvement an entity has with the origin, production, or bringing-into-existence of something.
-
C.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
D.
parentRelationship
Indicates a familial relationship in which one entity is the parent of another entity.
-
E.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
- 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d348868819083aec7a5da8c455b |
completed | April 1, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:17 p.m.