Triple
T2833058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victory Monument |
E62284
|
entity |
| Predicate | hasBusTerminalFunction |
P2423
|
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: [Victory Monument, hasBusTerminalFunction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusTerminalFunction Context triple: [Victory Monument, hasBusTerminalFunction, true]
-
A.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
-
B.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
-
C.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
D.
hasBusInterchange
chosen
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
-
E.
hasPassengerTerminalFacilities
Indicates that an entity provides facilities or infrastructure specifically intended for handling and serving passengers.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdec036dc8190bc2d974f6d82eda9 |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.