Triple
T31192652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crimson Dynamo |
E795222
|
entity |
| Predicate | technologyCounterpartOf |
P171624
|
FINISHED |
| Object | Iron Man armor |
—
|
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: Iron Man armor | Statement: [Crimson Dynamo, technologyCounterpartOf, Iron Man armor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyCounterpartOf Context triple: [Crimson Dynamo, technologyCounterpartOf, Iron Man armor]
-
A.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
B.
technologyComparableTo
Indicates that one technology can be meaningfully compared to another in terms of capability, performance, or relevant characteristics.
-
C.
technologyIncludes
Indicates that one technology encompasses, contains, or incorporates another technology as part of its components, features, or implementation.
-
D.
technologyName
Indicates the specific name or designation of a technology associated with an entity.
-
E.
technologyUsedBy
Indicates that a particular technology is employed or utilized by a specified entity.
- 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 9:08 p.m.