Triple
T14250613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Man |
E353249
|
entity |
| Predicate | signatureTechnology |
P113398
|
FINISHED |
| Object | arc reactor |
—
|
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: arc reactor | Statement: [Iron Man, signatureTechnology, arc reactor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureTechnology Context triple: [Iron Man, signatureTechnology, arc reactor]
-
A.
signatureConcept
Indicates that one concept is the defining or characteristic idea that most distinctly represents or identifies another concept.
-
B.
signatureType
Indicates the specific kind or category of a signature associated with an entity or action.
-
C.
signatureElement
Indicates that one entity is a component or part of another entity’s signature, such as a defining element within a formal or identifying representation.
-
D.
signatureManeuver
Indicates a distinctive or characteristic action or move that an entity is especially known for performing.
-
E.
signatureVehicle
Indicates that the vehicle is the primary or characteristic mode of transportation associated with a particular entity (such as a person, group, or brand).
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6296f9d0819086f62f525d07eb12 |
completed | April 14, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69de05c09b7881908acbca18bd7d997c |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239bd0f48190ada38c0261e0ef3c |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:08 a.m.