Triple
T28273258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragon Warrior |
E712911
|
entity |
| Predicate | notableBearerPersonality |
P202754
|
FINISHED |
| Object | enthusiastic |
—
|
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: enthusiastic | Statement: [Dragon Warrior, notableBearerPersonality, enthusiastic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBearerPersonality Context triple: [Dragon Warrior, notableBearerPersonality, enthusiastic]
-
A.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
B.
notableBearerFullName
Indicates that a full personal name is that of a notable or well-known bearer associated with the referenced entity.
-
C.
notableTraitOnStage
Indicates that an entity is characterized by a distinctive or noteworthy trait specifically in the context of performing or appearing on stage.
-
D.
notableCharacterName
Indicates that the subject has a notable or significant character whose name is given by the object.
-
E.
notableBearerNationality
Indicates that the subject has a notable bearer whose nationality is the specified object.
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_6a00b6199c348190b1e90375f737d026 |
completed | May 10, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a00b5169a7881909a07167c4188731f |
completed | May 10, 2026, 4:40 p.m. |
| PDg | Predicate description generation | batch_6a00b618cb10819095ccef12d8e303c5 |
completed | May 10, 2026, 4:45 p.m. |
Created at: April 27, 2026, 11:19 p.m.