Triple
T37423121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roncesvalles streetcar routes |
E929914
|
entity |
| Predicate | serveFunction |
P159622
|
FINISHED |
| Object | local transit |
—
|
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: local transit | Statement: [Roncesvalles streetcar routes, serveFunction, local transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serveFunction Context triple: [Roncesvalles streetcar routes, serveFunction, local transit]
-
A.
serviceModuleFunction
Indicates that a function is provided or performed by a specific service module within a system.
-
B.
mayServeFunction
chosen
Indicates that one entity is capable of performing, fulfilling, or acting in the role of a specified function for another entity or context.
-
C.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
D.
someServe
Indicates that one entity serves, assists, or performs duties for another entity in some capacity.
-
E.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a006fe981488190b4287289a3327664 |
completed | May 10, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_6a006f6976ec8190ba2c04fbaa946345 |
completed | May 10, 2026, 11:43 a.m. |
Created at: May 3, 2026, 4:16 p.m.