Triple
T10099999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spaklerweg |
E216173
|
entity |
| Predicate | hasTicketBarrierSystem |
P43416
|
FINISHED |
| Object | automatic fare gates |
—
|
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: automatic fare gates | Statement: [Spaklerweg, hasTicketBarrierSystem, automatic fare gates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketBarrierSystem Context triple: [Spaklerweg, hasTicketBarrierSystem, automatic fare gates]
-
A.
hasTicketBarrier
chosen
Indicates that an access-controlled barrier or gate is present, typically requiring a valid ticket or pass to pass through.
-
B.
hasTicketInspection
Indicates that a ticket is checked or verified by an authorized inspector or system.
-
C.
hasTicketBooths
Indicates that one entity possesses or contains ticket booths used for selling or distributing tickets.
-
D.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
E.
hasTicketHall
Indicates that a place or facility includes or is equipped with a designated ticket hall area for purchasing or validating tickets.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd07d686481908d9bb91392954474 |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:02 p.m.