Triple
T31507169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Chênes de Bouscaut (red) |
E803849
|
entity |
| Predicate | classificationRegion |
P173442
|
FINISHED |
| Object | Graves |
—
|
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: Graves | Statement: [Les Chênes de Bouscaut (red), classificationRegion, Graves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classificationRegion Context triple: [Les Chênes de Bouscaut (red), classificationRegion, Graves]
-
A.
classificationTest
Indicates that an entity is involved in or associated with a test or evaluation process used for classification purposes.
-
B.
classificationRole
Indicates that one entity serves as a classificatory role or type used to categorize or group another entity.
-
C.
classificationConsensus
Indicates that multiple agents or sources agree on the same classification or category assignment for a given entity or item.
-
D.
classificationIssue
Indicates that there is a problem, ambiguity, or error in how something has been categorized or assigned to a class or type.
-
E.
labelRegion
Indicates assigning a categorical or descriptive label to a specified region or area.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 30, 2026, 9:48 p.m.