Triple
T16808379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A5 |
E408536
|
entity |
| Predicate | isNumberedWithinSystem |
P37553
|
FINISHED |
| Object | Swiss A-number motorway system |
—
|
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: Swiss A-number motorway system | Statement: [A5, isNumberedWithinSystem, Swiss A-number motorway system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNumberedWithinSystem Context triple: [A5, isNumberedWithinSystem, Swiss A-number motorway system]
-
A.
isNumberedBy
chosen
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
B.
isNumbered
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
-
C.
isNumberedRelativeTo
Indicates that one entity’s numbering or ordinal position is defined or interpreted in relation to another entity.
-
D.
hasNumberingWithin
Indicates that one entity assigns or follows a specific numbering scheme within the scope or structure of another entity.
-
E.
isNumberedRouteIn
Indicates that a numbered route (such as a highway or road with an assigned number) is located within or passes through a specified geographic or administrative area.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cde590819080dc474292b023ee |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:22 a.m.