Triple
T13245924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermitage Water |
E315402
|
entity |
| Predicate | nearbyLandmarkType |
P90437
|
FINISHED |
| Object | medieval castle |
—
|
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: medieval castle | Statement: [Hermitage Water, nearbyLandmarkType, medieval castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyLandmarkType Context triple: [Hermitage Water, nearbyLandmarkType, medieval castle]
-
A.
typicalNearbyLandmarks
chosen
Indicates that certain landmarks are commonly found in the vicinity of a given place or location.
-
B.
nearbyFacilityType
Indicates that a facility of a specified type is located close to a given reference entity or location.
-
C.
proximityToLandmark
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
-
D.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
-
E.
notableNearbySite
Indicates that one entity is a significant or noteworthy site located close to 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d5c09f88190bb1566a6d8c073a6 |
completed | April 10, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69d98bcca7d88190a3e68e99ed3a29e6 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:23 p.m.