Triple
T27486529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gruyère cheese |
E693752
|
entity |
| Predicate | AOPRecognitionCountry |
P43832
|
FINISHED |
| Object | Switzerland |
—
|
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: Switzerland | Statement: [Gruyère cheese, AOPRecognitionCountry, Switzerland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AOPRecognitionCountry Context triple: [Gruyère cheese, AOPRecognitionCountry, Switzerland]
-
A.
identifiesCountryIn
Indicates that one entity specifies or determines which country another entity is associated with or located in.
-
B.
countryOfRecognition
chosen
Indicates the country that formally recognizes, acknowledges, or grants official status to a given entity.
-
C.
UNRecognizedCountry
Indicates that a country has been formally acknowledged as a sovereign state by the United Nations.
-
D.
accessCountry
Indicates that an entity has access to, operates within, or is associated with activities in a specified country.
-
E.
associatedCountryViaNotableBearer
Indicates a relationship where an entity is linked to a country through a notable person who bears or represents that entity (such as a name, title, or work).
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e8544ec8190864108497a8d8ad0 |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:02 p.m.