Triple
T27720475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | curanto |
E698938
|
entity |
| Predicate | curantoEnHoyoDefinition |
P162973
|
FINISHED |
| Object | curanto cooked in a pit in the ground |
—
|
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: curanto cooked in a pit in the ground | Statement: [curanto, curantoEnHoyoDefinition, curanto cooked in a pit in the ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curantoEnHoyoDefinition Context triple: [curanto, curantoEnHoyoDefinition, curanto cooked in a pit in the ground]
-
A.
correspondsToCavern
Indicates that one entity is associated with, matches, or represents a specific cavern in a defined correspondence relationship.
-
B.
containsCanyon
Indicates that one geographic or spatial entity includes a canyon within its boundaries or extent.
-
C.
containsGorge
Indicates that one entity geographically includes or encompasses a gorge within its area or boundaries.
-
D.
subterranean
Indicates that one entity is located beneath the surface of the ground or under another structure or area.
-
E.
burrowUse
Indicates that an entity makes use of a burrow, typically as a shelter, nesting site, or refuge.
- F. None of above. chosen
Provenance (4 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6363b50f08190a0d8e16d748388f5 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f6305219f08190b55f6193a4a49984 |
completed | May 2, 2026, 5:11 p.m. |
Created at: April 27, 2026, 3:06 p.m.