Triple
T9119051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pitripati |
E218797
|
entity |
| Predicate | titleEmphasizesRole |
P38167
|
FINISHED |
| Object | protector of departed ancestors |
—
|
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: protector of departed ancestors | Statement: [Pitripati, titleEmphasizesRole, protector of departed ancestors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleEmphasizesRole Context triple: [Pitripati, titleEmphasizesRole, protector of departed ancestors]
-
A.
titleOrRole
chosen
Indicates that one entity serves as the title, position, or role held or described by another entity.
-
B.
titleVariant
Indicates that one title is an alternative or variant form of another title referring to the same work or entity.
-
C.
titleIIFocus
Indicates that the primary focus or subject of a Title II–related provision, requirement, or classification is the referenced entity.
-
D.
titleRepresents
Indicates that a given title stands for, denotes, or symbolizes a particular concept, role, work, or entity.
-
E.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a7c6d48190a015efd17a017ca1 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.