Triple
T5147199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z |
E116100
|
entity |
| Predicate | serviceFrequencyContext |
P61818
|
FINISHED |
| Object | peak-direction rush hours |
—
|
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: peak-direction rush hours | Statement: [Z, serviceFrequencyContext, peak-direction rush hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceFrequencyContext Context triple: [Z, serviceFrequencyContext, peak-direction rush hours]
-
A.
serviceFrequencyType
Indicates how often a service occurs or is scheduled within a given time period.
-
B.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
C.
meetingFrequency
Indicates how often a meeting or recurring gathering takes place over a given period.
-
D.
performedFrequency
Indicates how often an action or activity is carried out within a given time period.
-
E.
typicalUpdateFrequency
Indicates how often an entity is usually updated or refreshed over time.
- 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_69bd4446c0e08190a7c29dc74976bf03 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd78d7f4d081908d59adcd86f52f1d |
completed | March 20, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69bd77ae2f10819098bb8939106e1281 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78d6a1388190804dcf568ca92129 |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:43 p.m.