Triple
T22192299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midmer-Losh pipe organ |
E548458
|
entity |
| Predicate | hasStops |
P146786
|
FINISHED |
| Object | over 450 |
—
|
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: over 450 | Statement: [Midmer-Losh pipe organ, hasStops, over 450]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStops Context triple: [Midmer-Losh pipe organ, hasStops, over 450]
-
A.
hasStopNear
Indicates that one entity has a stop or stopping point located in close proximity to another entity.
-
B.
hasStopoverState
Indicates that an entity’s journey or process includes an intermediate stop or temporary state before reaching its final destination or outcome.
-
C.
hasStopArea
Indicates that an entity is associated with or contains a specific stop area, such as a designated location where vehicles stop.
-
D.
hasStopType
Indicates that a stop or stopping point is classified as having a particular type or category of stop.
-
E.
isNonStop
Indicates that a service, trip, or process occurs from start to finish without any intermediate stops or interruptions.
- 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae49ec881908fa42446b19e3f2d |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e7222e74248190a2d3671049f117f2 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:35 p.m.