Triple
T29048473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cava de Viriato |
E735198
|
entity |
| Predicate | hasGeometricLayout |
P10827
|
FINISHED |
| Object | octagonal |
—
|
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: octagonal | Statement: [Cava de Viriato, hasGeometricLayout, octagonal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeometricLayout Context triple: [Cava de Viriato, hasGeometricLayout, octagonal]
-
A.
hasGeometry
Indicates that an entity is associated with a specific geometric representation or spatial form.
-
B.
hasLayout
chosen
Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of another entity.
-
C.
hasStandardLayout
Indicates that an entity follows a predefined or commonly accepted arrangement or structure.
-
D.
hasLayoutElement
Indicates that one entity includes, contains, or is associated with a specific layout element as part of its structural or visual arrangement.
-
E.
usesGridBasedLayout
Indicates that an entity arranges its elements or content according to a structured grid-based layout system.
- 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_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 28, 2026, 10:06 a.m.