Triple
T10438747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logan Express buses |
E246111
|
entity |
| Predicate | hasPrimaryRiders |
P12077
|
FINISHED |
| Object | airline passengers |
—
|
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: airline passengers | Statement: [Logan Express buses, hasPrimaryRiders, airline passengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryRiders Context triple: [Logan Express buses, hasPrimaryRiders, airline passengers]
-
A.
primaryRiders
chosen
Indicates that the referenced entities are the main or principal riders associated with a particular vehicle, trip, or ride-related event.
-
B.
hasOwnerRider
Indicates that an entity (such as an animal or vehicle) has a specific person who both owns it and rides or uses it.
-
C.
numberOfRiders
Indicates the total count of riders associated with a given entity or event.
-
D.
hasPrimarySeat
Indicates that one entity is designated as the main or principal seat, location, or position associated with another entity.
-
E.
hasSingleRiderLine
Indicates that a ride or attraction offers a dedicated line for solo riders, separate from the regular queue.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe083cd881909d2d8ad75d1d94cb |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:14 p.m.