Triple
T2501902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FMLN |
E52482
|
entity |
| Predicate | operatedAsUndergroundMovementUntil |
P40177
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [FMLN, operatedAsUndergroundMovementUntil, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAsUndergroundMovementUntil Context triple: [FMLN, operatedAsUndergroundMovementUntil, 1992]
-
A.
hasUndergroundSection
Indicates that an entity includes a portion or segment that is located below ground level.
-
B.
undergroundAlternateCommandCenter
Indicates a facility serving as a backup or secondary command center that is located underground.
-
C.
openedAsSubway
Indicates that a transportation facility or line originally began operation specifically as a subway service.
-
D.
firstSubwayOpeningSegment
Indicates that the subject is the initial segment or section of a subway line that was opened first in its operation or construction sequence.
-
E.
hasUndergroundSlide
Indicates that one entity features or includes an underground slide connecting it to another location or structure.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1c9f80c8190b40ada396e184e75 |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0bba5348190bb4637d3165cb339 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1aa13a08190a8757c017d8a2478 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:46 p.m.