Triple
T22041650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Charles Avenue streetcar line |
E544648
|
entity |
| Predicate | operatingAllYear |
P44053
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [St. Charles Avenue streetcar line, operatingAllYear, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatingAllYear Context triple: [St. Charles Avenue streetcar line, operatingAllYear, yes]
-
A.
operatedYearRound
Indicates that the subject entity functioned or was in operation continuously throughout the entire year, without seasonal closure.
-
B.
operatedInYear
Indicates that an entity was actively operating or functioning during a specified year.
-
C.
operatesAllTimes
Indicates that the action, service, or process is continuously in operation at all times without interruption.
-
D.
isUsedAllYear
Indicates that something is utilized or remains in active use throughout the entire year, without being limited to a particular season or period.
-
E.
isOpenAllYear
chosen
Indicates that the subject remains available or operational throughout the entire year without seasonal closures.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12829c1c081909edc7544242c9c7a |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:25 p.m.