Triple
T32780415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Côtes du Frontonnais |
E838337
|
entity |
| Predicate | successorAppellation |
P199817
|
FINISHED |
| Object | Fronton |
—
|
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: Fronton | Statement: [Côtes du Frontonnais, successorAppellation, Fronton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAppellation Context triple: [Côtes du Frontonnais, successorAppellation, Fronton]
-
A.
successorNamesake
Indicates that one entity is named after another entity that precedes it, typically as its successor or continuation in name.
-
B.
successorLabel
Indicates that one entity is the direct successor or next in sequence to another entity, often inheriting its role, position, or label.
-
C.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
D.
successorTitle
Indicates the title or position that directly follows and replaces a previous one in a sequence or succession.
-
E.
nicknameOfSuccessor
Indicates that one entity is a nickname or informal name used to refer to another entity that is its successor.
- F. None of above. chosen
Provenance (4 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
| PDg | Predicate description generation | batch_69ff59b1e2ac8190bb65529e9dbbb178 |
completed | May 9, 2026, 3:58 p.m. |
Created at: May 1, 2026, 1:14 a.m.