Triple
T3407740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bikin National Park |
E71814
|
entity |
| Predicate | isKeyAreaFor |
P10082
|
FINISHED |
| Object | conservation of Amur tiger |
—
|
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: conservation of Amur tiger | Statement: [Bikin National Park, isKeyAreaFor, conservation of Amur tiger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyAreaFor Context triple: [Bikin National Park, isKeyAreaFor, conservation of Amur tiger]
-
A.
isKeyRegionFor
chosen
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
-
B.
isInArea
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
C.
isKeyCrossingFor
Indicates that one entity serves as a primary or critical crossing point (such as a bridge, intersection, or passage) for another entity’s movement or connectivity.
-
D.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
E.
hasIconicArea
Indicates that an entity possesses a distinct, widely recognized area or region that is emblematic or characteristic of it.
- 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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8ede9c48190b13b0f5e7474e7fa |
completed | March 8, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69adadfa73ac8190a163f93e88d217f8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.