Triple
T11647272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Airport Train |
E276807
|
entity |
| Predicate | offersCheckIn |
P68242
|
FINISHED |
| Object | city check-in at Wien Mitte |
—
|
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: city check-in at Wien Mitte | Statement: [City Airport Train, offersCheckIn, city check-in at Wien Mitte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersCheckIn Context triple: [City Airport Train, offersCheckIn, city check-in at Wien Mitte]
-
A.
offersPass
Indicates that one entity provides or makes available a pass (such as a ticket, permit, or access credential) to another entity.
-
B.
offersActivity
Indicates that one entity provides or makes available a specific activity for another entity to participate in or use.
-
C.
offersAccess
chosen
Indicates that one entity provides another entity with the ability or permission to use, enter, or interact with a resource, service, or location.
-
D.
offersEvent
Indicates that an entity provides or makes available a specific event.
-
E.
offersProgram
Indicates that an entity provides or makes available a specific program (such as a course, curriculum, or initiative).
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cd9bb0819093d107204bed2fe0 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.