Triple
T21542631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quaggy |
E531529
|
entity |
| Predicate | hasGreenCorridorFunction |
P144169
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Quaggy, hasGreenCorridorFunction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGreenCorridorFunction Context triple: [Quaggy, hasGreenCorridorFunction, yes]
-
A.
hasGreenwaySegment
Indicates that an entity includes, is connected to, or is composed of one or more segments of a greenway path or corridor.
-
B.
hasGreenType
Indicates that an entity possesses or is associated with a type classified as green.
-
C.
hasGreenRuns
Indicates that an entity possesses or includes ski runs that are classified as green (i.e., beginner-level).
-
D.
hasAdjacentStationOnGreenLine
Indicates that one station is directly next to another station along the Green Line.
-
E.
hasServiceOnCorridor
Indicates that a service operates along, or is provided on, a specific corridor or route.
- 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb58c34808190b0eb54ba01e2cc13 |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:28 p.m.