Triple
T34492726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hesperange |
E885510
|
entity |
| Predicate | heritageStatusOfCastle |
P192088
|
FINISHED |
| Object | ruined 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: ruined castle | Statement: [Hesperange, heritageStatusOfCastle, ruined castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageStatusOfCastle Context triple: [Hesperange, heritageStatusOfCastle, ruined castle]
-
A.
heritageStatus
Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
-
B.
heritageStatusOf
Indicates that one entity holds a particular heritage designation or protection status in relation to another entity (such as a site, object, or tradition).
-
C.
heritageStatusOfCathedral
Indicates the heritage designation or protection status assigned to a cathedral.
-
D.
heritageStatusOfHostBuilding
Indicates the heritage protection or conservation status assigned to the host building.
-
E.
cityHeritageStatus
Indicates that a city holds a specific heritage designation or status, such as being recognized for its historical, cultural, or architectural significance.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 1, 2026, 2:01 a.m.