Triple
T2118934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier Cru |
E43871
|
entity |
| Predicate | canAppearWithVillageNameOnLabel |
P34941
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Premier Cru, canAppearWithVillageNameOnLabel, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canAppearWithVillageNameOnLabel Context triple: [Premier Cru, canAppearWithVillageNameOnLabel, true]
-
A.
isInVillage
Indicates that one entity is located within or belongs to the area defined as a village in relation to another entity.
-
B.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
C.
nativeLabel
Indicates the label or name of an entity expressed in its own native or original language.
-
D.
hasSignageName
Indicates that an entity has a specific name or label as it appears on its physical signage.
-
E.
hasToponymicUse
Indicates that a term or name is used as a toponym, i.e., as a place name or geographic designation.
- 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb3117c081908c5e748a869d1f9f |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:44 p.m.