Triple
T12673607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shiraz International Airport |
E302746
|
entity |
| Predicate | groundTransportMode |
P86086
|
FINISHED |
| Object | taxis |
—
|
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: taxis | Statement: [Shiraz International Airport, groundTransportMode, taxis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundTransportMode Context triple: [Shiraz International Airport, groundTransportMode, taxis]
-
A.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
B.
publicTransitMode
Indicates the type of public transportation (e.g., bus, train, subway) used or associated with a given trip or segment.
-
C.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
D.
transportModePresent
chosen
Indicates that a particular mode of transportation is involved or available in the described context or event.
-
E.
isPublicTransport
Indicates that the entity functions as a mode or instance of transportation that is available for use by the general public, typically operating on fixed routes or schedules.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961af991c8190b6079cb57e593b8f |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:20 p.m.