Triple
T13089437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Drain |
E310420
|
entity |
| Predicate | associatedWithPassengerType |
P99024
|
FINISHED |
| Object | commuters |
—
|
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: commuters | Statement: [The Drain, associatedWithPassengerType, commuters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPassengerType Context triple: [The Drain, associatedWithPassengerType, commuters]
-
A.
hasPassengerRole
Indicates that an entity participates in a context or event specifically in the capacity or role of a passenger.
-
B.
hasPassengerUsageCategory
Indicates the classification of how a passenger-related resource or service is used (e.g., its usage type or category for passengers).
-
C.
hasBoardingType
Indicates the specific manner or method by which an entity is boarded or accessed (e.g., how passengers or items are taken on).
-
D.
primaryPassengerGroup
chosen
Indicates the main group of passengers that is most directly associated with or served by a given entity or context.
-
E.
companionTicketType
Indicates the type or category of ticket that is associated with or issued to a companion of a primary ticket holder.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d98138a1d481908a139f2f67eb3472 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.