Triple
T13986329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amontillado |
E336449
|
entity |
| Predicate | isProtectedDesignation |
P40980
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Amontillado, isProtectedDesignation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProtectedDesignation Context triple: [Amontillado, isProtectedDesignation, yes]
-
A.
protectedDesignation
chosen
Indicates that one entity has an officially recognized and legally protected designation or status in relation to another entity.
-
B.
hasCriticalDesignation
Indicates that an entity has been assigned a status or label marking it as critical in importance, priority, or required attention.
-
C.
religiousDesignation
Indicates the specific religious role, status, or affiliation assigned to an entity.
-
D.
hasProtectedAreaStatus
Indicates that an area is officially designated and managed as a protected area under relevant conservation or legal frameworks.
-
E.
stateDesignation
Indicates that an entity has been formally assigned or recognized with a particular status, title, or classification by an official authority or governing body.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ea3e5a081908ed8ead108139252 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.