Triple
T16331212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Bob West |
E396555
|
entity |
| Predicate | hasCharacterAttribute |
P64980
|
FINISHED |
| Object | heroic |
—
|
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: heroic | Statement: [Captain Bob West, hasCharacterAttribute, heroic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacterAttribute Context triple: [Captain Bob West, hasCharacterAttribute, heroic]
-
A.
hasCharacterClass
Indicates that an entity (such as a character) belongs to or is assigned a particular character class or role type.
-
B.
hasCharacters
Indicates that an entity (such as a work or story) includes or features certain characters as part of its content.
-
C.
hasRoleCharacteristic
chosen
Indicates that an entity possesses a specific characteristic, quality, or attribute associated with a particular role.
-
D.
hasSupportingCharacterTrait
Indicates that a supporting character possesses a particular trait, quality, or characteristic.
-
E.
hasCharacterContext
Indicates that a character is associated with or participates in a particular contextual situation, setting, or state.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4dfd9688190a749e48ebc055baf |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.