Triple
T32502016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prineville District BLM |
E830685
|
entity |
| Predicate | typeOfUseManaged |
P202224
|
FINISHED |
| Object | recreation |
—
|
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: recreation | Statement: [Prineville District BLM, typeOfUseManaged, recreation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfUseManaged Context triple: [Prineville District BLM, typeOfUseManaged, recreation]
-
A.
usesManagementModel
Indicates that one entity applies, follows, or operates according to a particular management model in its management practices or structure.
-
B.
managementUse
Indicates that one entity uses or employs another entity specifically for management or administrative purposes.
-
C.
isManaged
Indicates that one entity exercises supervisory or administrative control over another entity.
-
D.
isManagedThrough
Indicates that one entity is administered, controlled, or operated by means of another entity, typically specifying the mechanism, channel, or system used for its management.
-
E.
isManagedWith
Indicates that one entity is administered, controlled, or operated using another entity as the managing tool, method, or resource.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a006417d1f4819093b2da02dbf2ab22 |
completed | May 10, 2026, 10:55 a.m. |
| PD | Predicate disambiguation | batch_6a00634a7a748190ac4774493fce3d30 |
completed | May 10, 2026, 10:51 a.m. |
| PDg | Predicate description generation | batch_6a006416f78081909b6ef047c531158d |
completed | May 10, 2026, 10:55 a.m. |
Created at: May 1, 2026, 12:59 a.m.