Triple
T7542012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omnitrans |
E178300
|
entity |
| Predicate | sbX |
P77903
|
FINISHED |
| Object | bus rapid transit line |
—
|
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 rapid transit line | Statement: [Omnitrans, sbX, bus rapid transit line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sbX Context triple: [Omnitrans, sbX, bus rapid transit line]
-
A.
by
Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified entity.
-
B.
hasSacbe
Indicates a relationship where one place or structure possesses, is connected by, or is associated with a sacbe (an ancient raised road or causeway).
-
C.
BAIs
Indicates that one entity is the base or foundation upon which another entity depends, is built, or is derived.
-
D.
usesSBox
Indicates that one entity employs or applies an S-box (substitution box) as part of its operation or process.
-
E.
باب
Indicates a relationship where one entity serves as a door, gate, or entry point to another entity, allowing or controlling access between them.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8750f80819088ddfb7a5580b5df |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:48 p.m.