Triple
T2955423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuemanco embarcadero |
E79920
|
entity |
| Predicate | heritageAspect |
P6203
|
FINISHED |
| Object | traditional agriculture |
—
|
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: traditional agriculture | Statement: [Cuemanco embarcadero, heritageAspect, traditional agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageAspect Context triple: [Cuemanco embarcadero, heritageAspect, traditional agriculture]
-
A.
heritageFunction
Indicates the role, use, or purpose that a heritage asset or element serves within its cultural, historical, or social context.
-
B.
heritageValue
Indicates that something possesses cultural, historical, or traditional significance that is valued and preserved as heritage.
-
C.
heritageType
Indicates the classification of an entity’s cultural or natural heritage category or type within a heritage framework.
-
D.
heritageField
chosen
Indicates that there is an association between an entity and a specific field, domain, or area related to cultural or historical heritage.
-
E.
heritageReference
Indicates that one entity serves as a cultural, historical, or heritage-related reference or source for 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99286ac8819084f02fbb0a1616d3 |
completed | March 8, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.