Triple
T8380575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TransLink |
E197675
|
entity |
| Predicate | modeManaged |
P81746
|
FINISHED |
| Object | bus |
—
|
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: bus | Statement: [TransLink, modeManaged, bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modeManaged Context triple: [TransLink, modeManaged, bus]
-
A.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
B.
modeType
Indicates the specific manner, method, or operational mode in which an action, process, or system is carried out or functions.
-
C.
mode
Indicates the manner, method, or way in which an action, process, or interaction is carried out or occurs.
-
D.
modeADescription
Indicates the descriptive text or explanation associated with a particular mode of operation or state.
-
E.
managedTo
Indicates that an entity successfully accomplished or achieved a particular action or outcome, often despite difficulty or obstacles.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80c57080819097eef2b7e46eaaee |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76da264881909483b835e1db06da |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6:02 p.m.