Triple
T24582978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobilis zones |
E608301
|
entity |
| Predicate | mainCityCovered |
P3940
|
FINISHED |
| Object | Lausanne |
—
|
NE NERFINISHED |
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: Lausanne | Statement: [Mobilis zones, mainCityCovered, Lausanne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCityCovered Context triple: [Mobilis zones, mainCityCovered, Lausanne]
-
A.
significantCityCovered
Indicates that a significant city lies within the geographic area or scope covered by something (such as a service, event, or phenomenon).
-
B.
coversCity
Indicates that one entity extends over, includes, or geographically encompasses the area of a specified city.
-
C.
servesAsFocusCityFor
Indicates that a city functions as a primary or designated focus city for an airline, organization, or transportation network, typically hosting significant but not hub-level operations or activities.
-
D.
alternativeCityServed
Indicates that one city functions as an alternative service location for another city, typically in contexts like transportation or logistics.
-
E.
primaryCity
chosen
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a984577881908c855f5e05756909 |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.