Triple
T28362534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jay Street–MetroTech |
E718400
|
entity |
| Predicate | complexUnified |
P169957
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Jay Street–MetroTech, complexUnified, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complexUnified Context triple: [Jay Street–MetroTech, complexUnified, 2010]
-
A.
complexName
Indicates that an entity has a multi-part or structurally intricate name, typically composed of several elements or components.
-
B.
launchComplexNumber
Indicates the identifying number assigned to a specific launch complex used for launching vehicles or spacecraft.
-
C.
hasComplexification
Indicates that one entity is a more complex or elaborated version, form, or development of another entity.
-
D.
isTotallyComplex
Indicates that something possesses a level of complexity that is complete, multifaceted, and not reducible to simpler or purely real/straightforward components.
-
E.
rangeComplex
Indicates that something extends or varies across a span of values, conditions, or states that are intricate, multi-faceted, or composed of multiple interacting parts.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f688d015908190ad5df37030ecf332 |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 28, 2026, 12:53 a.m.