Triple
T5622387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viva bus rapid transit |
E147637
|
entity |
| Predicate | startOperation |
P3267
|
FINISHED |
| Object | September 2005 |
—
|
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: September 2005 | Statement: [Viva bus rapid transit, startOperation, September 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOperation Context triple: [Viva bus rapid transit, startOperation, September 2005]
-
A.
operationStart
chosen
Indicates the point in time or event at which a specific operation or process begins.
-
B.
startProperty
Indicates that one entity marks the beginning or initial value/state of a property associated with another entity.
-
C.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
D.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
E.
inOperation
Indicates that an entity (such as a system, device, or facility) is currently active, functioning, and performing its intended operation.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c022133eec819086acb04864dde5ee |
completed | March 22, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.