Triple
T1149388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruter bus network |
E23639
|
entity |
| Predicate | contractsWith |
P16089
|
FINISHED |
| Object | private bus operating companies |
—
|
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: private bus operating companies | Statement: [Ruter bus network, contractsWith, private bus operating companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractsWith Context triple: [Ruter bus network, contractsWith, private bus operating companies]
-
A.
contractUnit
Indicates that one entity serves as a contractual unit or party within a contract relationship involving another entity.
-
B.
notableContract
chosen
Indicates that there exists a contract or agreement between entities that is of particular significance, prominence, or public interest.
-
C.
contractFeature
Indicates that one entity is a feature, term, or provision that is included in or associated with a particular contract.
-
D.
typeOfContract
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
E.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.