Triple
T24242086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEPTA Zone 5 |
E603256
|
entity |
| Predicate | fareTablePublishedBy |
P155316
|
FINISHED |
| Object | SEPTA |
—
|
NE NERFINISHED |
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: SEPTA | Statement: [SEPTA Zone 5, fareTablePublishedBy, SEPTA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareTablePublishedBy Context triple: [SEPTA Zone 5, fareTablePublishedBy, SEPTA]
-
A.
fareTableInclusion
Indicates that a particular fare is included within, or governed by, a specific fare table or pricing structure.
-
B.
fareDisplay
Indicates the action of presenting or showing fare information, such as prices or ticket options, for viewing or selection.
-
C.
fareBasis
Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
-
D.
fareContext
Indicates the pricing or fare-related conditions under which a transaction, service, or travel arrangement is applied.
-
E.
fareModel
Indicates a pricing relationship where a specific fare structure, rule set, or calculation method is applied to determine the cost of a trip or service.
- F. None of above. chosen
Provenance (4 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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28aa04fe08190922d6abde695571a |
completed | April 29, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:03 a.m.