Triple
T3682898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G-Mex tram stop |
E78150
|
entity |
| Predicate | systemOpeningPhase |
P22825
|
FINISHED |
| Object | Phase 1 of Manchester Metrolink |
—
|
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: Phase 1 of Manchester Metrolink | Statement: [G-Mex tram stop, systemOpeningPhase, Phase 1 of Manchester Metrolink]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemOpeningPhase Context triple: [G-Mex tram stop, systemOpeningPhase, Phase 1 of Manchester Metrolink]
-
A.
initialOpening
Indicates the first or earliest instance in which something is opened, begun, or made accessible.
-
B.
programPhase
chosen
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
C.
mainPhase
Indicates that an event, action, or state occurs during the primary or central phase of a larger process or sequence.
-
D.
system
Indicates that an entity functions as or belongs to a structured, organized set of components or processes that operate together as a system.
-
E.
bootProcess
Indicates the sequence of actions required to start up and initialize a system from a powered-off or reset 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_69ad85e18c1c8190be8aafb227f39f48 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4948cc48190ab1f59cc4a2437cc |
completed | March 8, 2026, 6:48 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.