Triple
T25223591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scar |
E632028
|
entity |
| Predicate | recognizesAsWarrior |
P159731
|
FINISHED |
| Object | Alexa "Lex" Woods |
—
|
NE NERFINISHED |
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: Alexa "Lex" Woods | Statement: [Scar, recognizesAsWarrior, Alexa "Lex" Woods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesAsWarrior Context triple: [Scar, recognizesAsWarrior, Alexa "Lex" Woods]
-
A.
warriorHolds
Indicates that a warrior is in possession of or currently holding an object or entity.
-
B.
isWarHeroOf
Indicates that one entity is recognized as a war hero in relation to, or on behalf of, another entity (such as a country, group, or cause).
-
C.
wearsArmorOf
Indicates that one entity is equipped with or dressed in the specific armor that belongs to or is associated with another entity.
-
D.
wearsArmor
Indicates that an entity is equipped with or dressed in armor as protective gear.
-
E.
hasFighter
Indicates that an entity possesses, controls, or is associated with a fighter (such as a combatant, combat vehicle, or fighting unit).
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5f7a205688190b8f36bff5013247c |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 21, 2026, 1:03 p.m.