Triple
T29048489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cava de Viriato |
E735198
|
entity |
| Predicate | hasPerimeterType |
P1972
|
FINISHED |
| Object | earthen ramparts |
—
|
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: earthen ramparts | Statement: [Cava de Viriato, hasPerimeterType, earthen ramparts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerimeterType Context triple: [Cava de Viriato, hasPerimeterType, earthen ramparts]
-
A.
hasPerimeterTrack
Indicates that an entity is equipped with or surrounded by a designated track running around its perimeter.
-
B.
hasBoundaryType
chosen
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
-
C.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
D.
hasBoundaryShape
Indicates that an entity is associated with, or characterized by, a specific geometric or spatial shape of its boundary.
-
E.
hasQuadrangleType
Indicates that an entity is associated with, or classified by, a specific type or category of quadrangle.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 28, 2026, 10:06 a.m.