Triple
T18036820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laguiole cheese |
E431527
|
entity |
| Predicate | labelMarking |
P99152
|
FINISHED |
| Object | Laguiole name and identification number on rind |
—
|
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: Laguiole name and identification number on rind | Statement: [Laguiole cheese, labelMarking, Laguiole name and identification number on rind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelMarking Context triple: [Laguiole cheese, labelMarking, Laguiole name and identification number on rind]
-
A.
distinctiveMarking
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
-
B.
mayHaveMarkings
Indicates that an entity is permitted or able to possess certain markings or distinguishing signs.
-
C.
labelIndication
Indicates that a label or designation is assigned to an entity to specify its indication, purpose, or intended use.
-
D.
markingFeature
chosen
Indicates a feature that serves as a distinguishing mark or identifier associated with an entity.
-
E.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be3a80508190b667c3f6d14f5c84 |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.