Triple
T15335414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyoda |
E366650
|
entity |
| Predicate | hasPreservationArea |
P855
|
FINISHED |
| Object | castle town district |
—
|
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: castle town district | Statement: [Gyoda, hasPreservationArea, castle town district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreservationArea Context triple: [Gyoda, hasPreservationArea, castle town district]
-
A.
isPreservedArea
Indicates that an area is legally or formally protected to maintain its natural, historical, or cultural state and prevent alteration or development.
-
B.
hasProtectedArea
chosen
Indicates that an entity possesses, includes, or is associated with a designated protected area for conservation or restricted use.
-
C.
hasProtectedAreaStatus
Indicates that an area is officially designated and managed as a protected area under relevant conservation or legal frameworks.
-
D.
hasProtectedAreaCoverage
Indicates that a specified portion or extent of an area falls within officially designated protected areas.
-
E.
regionOfPreservation
Indicates the specific area or portion of an object or specimen where preservation has occurred or is observed.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e03c5f081908e4d14dbdbc7f7a6 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.