Triple
T11200230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuco |
E265018
|
entity |
| Predicate | relationshipWithAngelEyes |
P97827
|
FINISHED |
| Object | enemy |
—
|
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: enemy | Statement: [Tuco, relationshipWithAngelEyes, enemy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithAngelEyes Context triple: [Tuco, relationshipWithAngelEyes, enemy]
-
A.
associatedWithArchangelName
Indicates that something has a connection or linkage to a specific archangel’s name.
-
B.
revelationAngel
Indicates that an angel is the one who delivers or mediates a divine revelation to someone or about something.
-
C.
angelicHierarchy
Indicates a hierarchical relationship in which one angelic being holds a higher or lower rank or order relative to another within a structured celestial order.
-
D.
hasProtagonistRelationship
Indicates that there exists a central, story-driving relationship involving the protagonist and another entity within a narrative.
-
E.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c1e9f88190b2b42326aba9d778 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:29 p.m.