Triple
T37495890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bremerton–Port Orchard foot ferry |
E931825
|
entity |
| Predicate | typicalTripPurpose |
P24037
|
FINISHED |
| Object | work commute |
—
|
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: work commute | Statement: [Bremerton–Port Orchard foot ferry, typicalTripPurpose, work commute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTripPurpose Context triple: [Bremerton–Port Orchard foot ferry, typicalTripPurpose, work commute]
-
A.
typicalJourneyPurpose
chosen
Indicates the usual or most common reason or objective for which an entity undertakes a journey.
-
B.
journeyPurpose
Indicates the reason or intended goal motivating an entity’s journey or trip.
-
C.
typicalTravelCategory
Indicates the usual or most common type of travel associated with an entity, such as its primary travel purpose or category.
-
D.
bookingPurpose
Indicates the reason or intended use for which a booking or reservation is made.
-
E.
transportPurpose
Indicates that one entity is transported or moved specifically for the purpose, goal, or intended use denoted by another entity.
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.