Triple
T36526768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vosges forests |
E900326
|
entity |
| Predicate | highestZonesCharacterizedBy |
P163832
|
FINISHED |
| Object | montane forest |
—
|
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: montane forest | Statement: [Vosges forests, highestZonesCharacterizedBy, montane forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestZonesCharacterizedBy Context triple: [Vosges forests, highestZonesCharacterizedBy, montane forest]
-
A.
highestZones
Indicates that the related zones are those with the maximum or topmost value (e.g., elevation, priority, or intensity) among a set of zones.
-
B.
higherZonesContribution
Indicates that one entity contributes more or plays a greater role in higher zones or levels than another entity.
-
C.
characteristicOfZone
chosen
Indicates that a particular characteristic, feature, or property is associated with and defines a specific zone or area.
-
D.
highestOrgan
Indicates that one entity is the organ with the highest rank, level, or position within a specified system or hierarchy relative to another entity.
-
E.
highestPart
Indicates that one entity is the topmost or uppermost portion of 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_69f76e5eedb88190a393b8c623f71dd7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 3, 2026, 4:11 p.m.