Triple
T15927768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lex Luger |
E386245
|
entity |
| Predicate | usedGimmick |
P71441
|
FINISHED |
| Object | All-American hero |
—
|
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: All-American hero | Statement: [Lex Luger, usedGimmick, All-American hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedGimmick Context triple: [Lex Luger, usedGimmick, All-American hero]
-
A.
gimmick
chosen
Indicates that an entity uses or features a novel, attention-grabbing trick or device primarily intended to attract interest rather than provide substantive value.
-
B.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
C.
usedBoonsFrom
Indicates that one entity has utilized or expended beneficial effects, powers, or advantages that originated from another entity.
-
D.
usedOrb
Indicates that an entity made use of or employed an orb to perform an action or achieve some effect.
-
E.
trophyUse
Indicates that an entity uses, employs, or utilizes a trophy in some manner or context.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.