Triple
T20527067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Segovia Aqueduct |
E503964
|
entity |
| Predicate | hasLowerArcade |
P24796
|
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: [Segovia Aqueduct, hasLowerArcade, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowerArcade Context triple: [Segovia Aqueduct, hasLowerArcade, yes]
-
A.
hasArcades
chosen
Indicates that one entity features or contains arcaded structures (a series of arches or covered passageways) associated with another entity.
-
B.
hasLowerTier
Indicates that one entity is ranked, valued, or classified at a lower level or tier relative to another entity.
-
C.
hasLowerDeckFunction
Indicates that an entity serves a specific role or performs a designated function on the lower deck of a structure or vehicle.
-
D.
hasLowerPart
Indicates that one entity includes another entity as a component specifically located in its lower part or region.
-
E.
hasLowerCave
Indicates that one location or structure possesses or is associated with another cave situated at a lower level or beneath it.
- 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a066402081909dd53830eb637ad0 |
completed | April 20, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:37 a.m.