Triple
T29467828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow railway stations |
E747426
|
entity |
| Predicate | hasBaggageServices |
P30409
|
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: [Moscow railway stations, hasBaggageServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaggageServices Context triple: [Moscow railway stations, hasBaggageServices, yes]
-
A.
hasBaggageService
chosen
Indicates that an entity provides or supports services related to handling, storing, or managing baggage for others.
-
B.
hasBaggageCheck
Indicates that an entity provides or is associated with a service or facility for checking in baggage.
-
C.
hasCheckedBaggage
Indicates that an entity is associated with baggage that has been checked in for transport, typically for a trip or flight.
-
D.
hasBaggageClaim
Indicates that a location, typically a transportation hub, includes or provides a baggage claim area for retrieving luggage.
-
E.
hasPassengerAirlineService
Indicates that a location or facility is served by scheduled passenger airline flights.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 28, 2026, 3:54 p.m.