Triple
T30663794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steel Vengeance |
E780602
|
entity |
| Predicate | builtOnStructureOf |
P2012
|
FINISHED |
| Object | Mean Streak |
—
|
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: Mean Streak | Statement: [Steel Vengeance, builtOnStructureOf, Mean Streak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtOnStructureOf Context triple: [Steel Vengeance, builtOnStructureOf, Mean Streak]
-
A.
builtStructureFor
Indicates that one entity constructed or assembled a structure specifically intended for the use, benefit, or purpose of another entity.
-
B.
builtOn
chosen
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
C.
builtInThe
Indicates that something was constructed or created within a specified location, structure, or context.
-
D.
buildingStructure
Indicates that one entity is a structural component or physical part that forms, supports, or constitutes the construction of another entity.
-
E.
builtInfrastructureType
Indicates the specific kind or category of built infrastructure associated with or characterized by the subject.
- 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68ae29de08190be2cd4d95c0fa0a4 |
completed | May 2, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:31 p.m.