Triple
T16639080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrono app |
E404282
|
entity |
| Predicate | providesInformationFor |
P98094
|
FINISHED |
| Object | buses in Montreal area |
—
|
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: buses in Montreal area | Statement: [Chrono app, providesInformationFor, buses in Montreal area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesInformationFor Context triple: [Chrono app, providesInformationFor, buses in Montreal area]
-
A.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
B.
providedInformationOn
Indicates that one entity supplied or communicated specific information or details to another entity.
-
C.
providedInformationTo
Indicates that one entity has supplied or communicated information to another entity.
-
D.
offersInformationOn
chosen
Indicates that one entity provides or makes available information about another entity or topic.
-
E.
collectsInformationOn
Indicates that one entity gathers or acquires data, facts, or details about another entity.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37acff38081908c8044936b794ce0 |
completed | April 18, 2026, 12:36 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:18 a.m.