Triple
T1791833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Day Convenience Pass |
E39512
|
entity |
| Predicate | providerType |
P17473
|
FINISHED |
| Object | public transportation agency |
—
|
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: public transportation agency | Statement: [One Day Convenience Pass, providerType, public transportation agency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providerType Context triple: [One Day Convenience Pass, providerType, public transportation agency]
-
A.
typicalProvider
chosen
Indicates that one entity commonly or characteristically serves as a provider of goods, services, or resources to another entity.
-
B.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
C.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
-
D.
packageType
Indicates the classification or category of packaging associated with an item or shipment.
-
E.
payerType
Indicates the type or category of entity responsible for making a payment in the relationship.
- 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.