Triple
T36629137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Périgord |
E904261
|
entity |
| Predicate | correspondsToModernDepartment |
P84931
|
FINISHED |
| Object | Dordogne |
—
|
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: Dordogne | Statement: [Périgord, correspondsToModernDepartment, Dordogne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToModernDepartment Context triple: [Périgord, correspondsToModernDepartment, Dordogne]
-
A.
partlyCorrespondsToModernDepartment
chosen
Indicates that an entity’s historical or former administrative area overlaps only in part with the boundaries of a specified modern department.
-
B.
locatedInModernDepartment
Indicates that an entity is geographically situated within the boundaries of a present-day administrative department.
-
C.
largestModernDepartment
Indicates that one entity is the largest modern department (by size, scope, or another defined metric) in relation to a specified set or context.
-
D.
recognizesDepartment
Indicates that one entity formally acknowledges or accepts another entity as a valid or official department.
-
E.
worksInDepartment
Indicates that an entity is employed in and performs their job duties within a particular department.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:11 p.m.