Triple
T31203642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central France |
E795541
|
entity |
| Predicate | locatedAwayFrom |
P91083
|
FINISHED |
| Object | French coasts |
—
|
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: French coasts | Statement: [Central France, locatedAwayFrom, French coasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAwayFrom Context triple: [Central France, locatedAwayFrom, French coasts]
-
A.
awayFrom
chosen
Indicates that one entity is located at a distance from, or moving farther away from, another entity.
-
B.
locatedOff
Indicates that one entity is situated away from, but in the vicinity of, another entity or reference point, rather than directly on or within it.
-
C.
locatedOutsideJurisdiction
Indicates that one entity is situated beyond the legal or administrative authority area of another entity or governing body.
-
D.
isFurtherFrom
Indicates that one entity is at a greater distance from a reference point or object than another entity is.
-
E.
geographicallySeparatedFrom
Indicates that two places or regions are distinct and apart from each other in physical location or geographic space.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a016777257081908841c5522dfa76e6 |
completed | May 11, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_6a0164e49bec8190af3c8626be9677a9 |
completed | May 11, 2026, 5:11 a.m. |
Created at: April 29, 2026, 9:09 p.m.