Triple
T20041357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Almansa |
E497426
|
entity |
| Predicate | castleBuiltOn |
P138466
|
FINISHED |
| Object | rocky hill |
—
|
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: rocky hill | Statement: [Almansa, castleBuiltOn, rocky hill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: castleBuiltOn Context triple: [Almansa, castleBuiltOn, rocky hill]
-
A.
castleBuilt
Indicates that a castle has been constructed or established, typically by a specific agent or during a particular time period.
-
B.
castleBuiltOf
Indicates that a castle is constructed primarily from a specified material.
-
C.
castleBuiltFor
Indicates that a castle was constructed specifically for the benefit, use, or commission of a particular person, group, or purpose.
-
D.
fortressBuiltAs
Indicates that a fortress was originally constructed to serve as a particular type, role, or function.
-
E.
castleLocatedIn
Indicates that a castle is situated within or belongs to a specific geographic or administrative location.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662eb9a6081909d06dc1d457b4d5a |
completed | April 20, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:37 p.m.