Triple
T34175235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terrasson-Lavilledieu (Corrèze part) |
E876649
|
entity |
| Predicate | sharesCommuneWith |
P32181
|
FINISHED |
| Object | Terrasson-Lavilledieu (Dordogne part) |
—
|
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: Terrasson-Lavilledieu (Dordogne part) | Statement: [Terrasson-Lavilledieu (Corrèze part), sharesCommuneWith, Terrasson-Lavilledieu (Dordogne part)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCommuneWith Context triple: [Terrasson-Lavilledieu (Corrèze part), sharesCommuneWith, Terrasson-Lavilledieu (Dordogne part)]
-
A.
sharesCommunityWith
chosen
Indicates that two entities belong to or participate in the same community or communal group.
-
B.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
C.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
D.
sharesHomeWith
Indicates that two entities live in the same home or residence.
-
E.
sharesElementsWith
Indicates that two entities have one or more elements or components in common.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fffc783b648190bcd7df017514d206 |
completed | May 10, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69fffc03fa24819099e12413dc6e0afd |
completed | May 10, 2026, 3:31 a.m. |
Created at: May 1, 2026, 1:54 a.m.