Triple
T11283371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lully (Geneva) |
E267119
|
entity |
| Predicate | hasLocalRoads |
P49867
|
FINISHED |
| Object | communal roads of Bernex |
—
|
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: communal roads of Bernex | Statement: [Lully (Geneva), hasLocalRoads, communal roads of Bernex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalRoads Context triple: [Lully (Geneva), hasLocalRoads, communal roads of Bernex]
-
A.
hasLocalRoad
chosen
Indicates that there exists a local road connection or association between the related entities.
-
B.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
-
C.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
D.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an entity.
-
E.
hasRoadBoundary
Indicates that a road segment is associated with a specific boundary or edge that defines its lateral limits.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e96e15708190b3a1cccfbbe65882 |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:31 p.m.