Triple
T24465710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cognac region |
E616960
|
entity |
| Predicate | oakSourceRegion |
P410
|
FINISHED |
| Object | Limousin |
—
|
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: Limousin | Statement: [Cognac region, oakSourceRegion, Limousin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oakSourceRegion Context triple: [Cognac region, oakSourceRegion, Limousin]
-
A.
sourceRegion
chosen
Indicates the geographic or spatial region from which something originates or is derived.
-
B.
partOfForestRegion
Indicates that one entity is a component or subdivision within a larger forest region.
-
C.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
-
D.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
E.
observedInRegion
Indicates that something has been detected, recorded, or seen occurring within a specified geographic or spatial region.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2993ecd988190991598832b29a131 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:19 a.m.