Triple
T38561758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MVG |
E928093
|
entity |
| Predicate | providesInfrastructureType |
P2560
|
FINISHED |
| Object | bus stops |
—
|
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 stops | Statement: [MVG, providesInfrastructureType, bus stops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesInfrastructureType Context triple: [MVG, providesInfrastructureType, bus stops]
-
A.
isPartOfInfrastructureType
Indicates that something belongs to, or is categorized under, a specific type of infrastructure.
-
B.
hasInfrastructureType
chosen
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
-
C.
overseesInfrastructureType
Indicates that one entity is responsible for supervising, managing, or regulating a particular type or category of infrastructure.
-
D.
typicalInfrastructure
Indicates that something is part of the standard or commonly expected infrastructure associated with a given context or entity.
-
E.
isPartOfInfrastructure
Indicates that something belongs to, is included within, or functions as a component of a larger infrastructure system.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff0e9c75208190a4423261f00b79b3 |
completed | May 9, 2026, 10:38 a.m. |
| PD | Predicate disambiguation | batch_69ff0e07f08481909c4ae322632a6bf0 |
completed | May 9, 2026, 10:35 a.m. |
Created at: May 3, 2026, 4:32 p.m.