Triple
T8860510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serra da Estrela |
E210874
|
entity |
| Predicate | cheeseHasStatus |
P15010
|
FINISHED |
| Object | PDO |
—
|
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: PDO | Statement: [Serra da Estrela, cheeseHasStatus, PDO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cheeseHasStatus Context triple: [Serra da Estrela, cheeseHasStatus, PDO]
-
A.
hasStatusIn
chosen
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
-
B.
seeksStatusAs
Indicates that one entity is attempting to obtain or be recognized with a particular status, role, or standing in relation to another entity.
-
C.
hasUnitStatus
Indicates that an entity is associated with a particular operational or condition status as a unit.
-
D.
chartStatus
Indicates the current state or condition of a chart, such as whether it is active, updated, or in a particular workflow stage.
-
E.
hasStatusLabel
Indicates that an entity is associated with a specific status expressed as a human-readable label.
- 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e712d08190bfb1c4ba3acaea90 |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:50 p.m.