Triple
T37715989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Lad |
E939453
|
entity |
| Predicate | basedOnFutureSelf |
P153109
|
FINISHED |
| Object | Kang the Conqueror |
—
|
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: Kang the Conqueror | Statement: [Iron Lad, basedOnFutureSelf, Kang the Conqueror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnFutureSelf Context triple: [Iron Lad, basedOnFutureSelf, Kang the Conqueror]
-
A.
laterMotivation
Indicates that one event, state, or action serves as a motivation or reason for another event, state, or action that occurs later in time.
-
B.
basedOnBelief
Indicates that one entity’s action, decision, or assertion is grounded in, motivated by, or derived from a particular belief held by that entity.
-
C.
willBecome
chosen
Indicates that one entity is expected or destined to change state or identity into another entity in the future.
-
D.
selfDetermination
Indicates that an entity independently determines its own course of action, decisions, or status without external control or imposition.
-
E.
laterBelief
Indicates that an agent holds a particular belief at a time that is later than some referenced earlier time or belief 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:18 p.m.