Triple
T27052868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild Forest |
E684821
|
entity |
| Predicate | landUseEmphasis |
P162036
|
FINISHED |
| Object | multiple use |
—
|
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: multiple use | Statement: [Wild Forest, landUseEmphasis, multiple use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landUseEmphasis Context triple: [Wild Forest, landUseEmphasis, multiple use]
-
A.
landUseContext
Indicates the contextual setting or circumstances under which a particular piece of land is used or designated for a specific purpose.
-
B.
landUseIncludes
Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
-
C.
majorLandUse
Indicates the primary way a given area of land is utilized or designated (e.g., residential, commercial, agricultural).
-
D.
primaryLandUse
Indicates the main or dominant way in which a given piece of land is utilized or designated (e.g., residential, agricultural, commercial).
-
E.
landUsePlanning
Indicates the relationship in which an authority or agent organizes, regulates, or designates how land and space may be used or developed within a given area.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f622b145848190b67cfdc47da6a887 |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621c7d3e0819095b1f327637ae4f9 |
completed | May 2, 2026, 4:09 p.m. |
Created at: April 27, 2026, 8:15 a.m.