Triple
T2208364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French autoroute network |
E50854
|
entity |
| Predicate | restAreas |
P29828
|
FINISHED |
| Object | present at regular intervals |
—
|
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: present at regular intervals | Statement: [French autoroute network, restAreas, present at regular intervals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restAreas Context triple: [French autoroute network, restAreas, present at regular intervals]
-
A.
hasRestAreas
chosen
Indicates that a route, location, or facility includes one or more designated rest areas available for use.
-
B.
touringArea
Indicates that an entity is designated as an area or region where touring or guided visits take place.
-
C.
tourismRegion
Indicates that a place or area is designated or recognized as a tourism region associated with another geographic or administrative entity.
-
D.
placesWithin
Indicates that one place or area is located entirely inside the boundaries of another place or area.
-
E.
arealRegion
Indicates that something occupies or pertains to a specific two-dimensional geographic or spatial 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc1baa0948190b07ffc347a4f714e |
completed | March 7, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69abbda8a6dc8190aa855ce2d17194b1 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.