Triple
T11972085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château Suduiraut |
E284944
|
entity |
| Predicate | AXAMillesimesRole |
P102575
|
FINISHED |
| Object | wine estate management company |
—
|
LITERAL FINISHED |
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: wine estate management company | Statement: [Château Suduiraut, AXAMillesimesRole, wine estate management company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AXAMillesimesRole Context triple: [Château Suduiraut, AXAMillesimesRole, wine estate management company]
-
A.
CorwinRole
Indicates that an entity holds or is assigned a specific role or function in relation to Corwin.
-
B.
roleAtMidway
Indicates that an entity holds or held a specific role, position, or function at the midpoint or intermediate stage of a process, event, or time period.
-
C.
antRole
Indicates that one entity has a specific role, function, or responsibility in relation to another entity.
-
D.
serpentRole
Indicates that an entity functions in the role or capacity of a serpent within a given context or relationship.
-
E.
MiramboRole
Indicates that an entity holds a specific role, position, or function in relation to Mirambo.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037d32e88190b1509285dc907d29 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:46 p.m.