Triple
T15577504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle Enterprise |
E374405
|
entity |
| Predicate | ferryFlightToNewYork |
P119261
|
FINISHED |
| Object | 2012-04-27 |
—
|
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: 2012-04-27 | Statement: [Space Shuttle Enterprise, ferryFlightToNewYork, 2012-04-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ferryFlightToNewYork Context triple: [Space Shuttle Enterprise, ferryFlightToNewYork, 2012-04-27]
-
A.
hasFerryService
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
B.
ferryOperator
Indicates that one entity operates, manages, or runs a ferry service for another entity or in a particular context.
-
C.
hasFerryPort
Indicates that a place serves as a location where ferries regularly dock to load and unload passengers or cargo.
-
D.
hasNearbyFerryRoute
Indicates that there is a ferry route located close to the referenced entity.
-
E.
travelTimeByFerry
Indicates the duration required to travel between two locations specifically using a ferry as the mode of transportation.
- F. None of above. chosen
Provenance (4 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e22c89081909b1ec0cd36a1ef45 |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:11 a.m.