Triple
T15731318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Riga |
E381350
|
entity |
| Predicate | isConservationArea |
P103372
|
FINISHED |
| Object | partly true |
—
|
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: partly true | Statement: [Mount Riga, isConservationArea, partly true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConservationArea Context triple: [Mount Riga, isConservationArea, partly true]
-
A.
hasConservationLand
Indicates that an entity possesses, manages, or is associated with land designated for environmental or natural resource conservation.
-
B.
hasConservationFocusArea
Indicates that an entity is associated with a specific area or domain that is the focus of its conservation efforts or activities.
-
C.
establishedAsConservationArea
chosen
Indicates that a location or region has been officially designated and protected as a conservation area.
-
D.
isTypeOfProtectedArea
Indicates that one entity is classified as a specific type or category of protected area in relation to another entity.
-
E.
isScenicArea
Indicates that a location is recognized as a scenic area, typically valued for its natural beauty or visually appealing surroundings.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb61cb881908b158609c1ccfa1e |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.