Triple
T3542035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland Transit Mall |
E74908
|
entity |
| Predicate | usesModeOfTransport |
P28705
|
FINISHED |
| Object | bus |
—
|
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: bus | Statement: [Portland Transit Mall, usesModeOfTransport, bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesModeOfTransport Context triple: [Portland Transit Mall, usesModeOfTransport, bus]
-
A.
hasPublicTransportUsage
Indicates that an entity makes use of, or is associated with the use of, public transportation services.
-
B.
passesUsedForTransportation
Indicates that the passes are utilized as a means or instrument for transporting people or goods.
-
C.
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.
-
D.
transportAssumption
Indicates an assumption that something can be transported or carried from one place or context to another.
-
E.
publicTransitMode
chosen
Indicates the type of public transportation (e.g., bus, train, subway) used or associated with a given trip or segment.
- 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbf73c5e881909a8352512928377b |
completed | March 8, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69adae15749881909b847c6ca73c934e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.