Triple
T19878227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tour de Carbonnière |
E477695
|
entity |
| Predicate | roadPassedThrough |
P30397
|
FINISHED |
| Object | medieval access road to Aigues-Mortes |
—
|
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: medieval access road to Aigues-Mortes | Statement: [Tour de Carbonnière, roadPassedThrough, medieval access road to Aigues-Mortes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadPassedThrough Context triple: [Tour de Carbonnière, roadPassedThrough, medieval access road to Aigues-Mortes]
-
A.
roadTraverses
chosen
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
-
B.
roadPassType
Indicates the type or category of permission or authorization required to use or pass along a particular road or route.
-
C.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
-
D.
crossedByHighway
Indicates that a highway passes across or through the extent of a given entity or area.
-
E.
isRoadPass
Indicates that a particular road or route is currently passable or open for travel.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658dc8ce08190b005ad49924e5659 |
completed | April 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.