Triple
T6997926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parmigiano Reggiano |
E162263
|
entity |
| Predicate | rindMarking |
P53131
|
FINISHED |
| Object | dotted inscription of the name on the 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: dotted inscription of the name on the rind | Statement: [Parmigiano Reggiano, rindMarking, dotted inscription of the name on the rind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rindMarking Context triple: [Parmigiano Reggiano, rindMarking, dotted inscription of the name on the rind]
-
A.
eggMarkings
Indicates that one entity bears or displays specific markings or patterns on its eggs in relation to another entity or context.
-
B.
distinctiveMarking
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
-
C.
colorOfTrailMarkings
Indicates the relationship specifying what color the trail’s markings are.
-
D.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
E.
rindType
chosen
Indicates the type or characteristic of the rind associated with an 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbeef57881909245c8a5374a8111 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.