Triple
T16013707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ploshchad Gagarina station |
E388405
|
entity |
| Predicate | ticketBarrierSystem |
P43416
|
FINISHED |
| Object | automatic turnstiles |
—
|
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 turnstiles | Statement: [Ploshchad Gagarina station, ticketBarrierSystem, automatic turnstiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketBarrierSystem Context triple: [Ploshchad Gagarina station, ticketBarrierSystem, automatic turnstiles]
-
A.
hasTicketBarrier
chosen
Indicates that an access-controlled barrier or gate is present, typically requiring a valid ticket or pass to pass through.
-
B.
parkEntranceStation
Indicates that a location functions as an entrance station or access point for a park.
-
C.
hasTicketInspection
Indicates that a ticket is checked or verified by an authorized inspector or system.
-
D.
ticketMachines
Indicates that there is a relationship involving ticket machines, typically denoting where they are located, available, or associated with a particular entity or place.
-
E.
ticketAcceptanceArea
Indicates the geographic or operational area within which a given ticket is valid for use or accepted as proof of payment.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:55 a.m.