Triple
T37421023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D1504 road |
E929851
|
entity |
| Predicate | isKeyConnectorIn |
P97647
|
FINISHED |
| Object | Savoie region |
—
|
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: Savoie region | Statement: [D1504 road, isKeyConnectorIn, Savoie region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyConnectorIn Context triple: [D1504 road, isKeyConnectorIn, Savoie region]
-
A.
isKeyConnectionPointFor
chosen
Indicates that something serves as a primary or critical linking point that connects or integrates other elements within a system or structure.
-
B.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
-
C.
isMajorConnectorFor
Indicates that one entity serves as a primary or critical linkage or pathway connecting other entities within a system or network.
-
D.
isShortConnector
Indicates that one entity functions as a connector or link between other entities and is characterized by having a short length or duration.
-
E.
isInKey
Indicates that something is located within, or belongs to, a specified key or key-based grouping in a structured 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.