Triple
T13856233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Picpus |
E333070
|
entity |
| Predicate | isUndergroundStation |
P49108
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Picpus, isUndergroundStation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUndergroundStation Context triple: [Picpus, isUndergroundStation, true]
-
A.
hasSubwayStationEntrance
Indicates that one entity serves as an entrance or access point to a subway station associated with another entity.
-
B.
subwayStation
Indicates that one entity is a subway station associated with, located in, or serving the other entity.
-
C.
isPublicTransportStation
chosen
Indicates that a location functions as a station or stop used by public transportation services such as buses, trains, trams, or subways.
-
D.
hasUndergroundSection
Indicates that an entity includes a portion or segment that is located below ground level.
-
E.
hasSubwayLineAboveOrBelow
Indicates that one subway line is physically located above or below another subway line, such as on different levels of a transit system.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02dc9f488190b7181dcb7e304632 |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.