Triple
T1219203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia Range |
E26178
|
entity |
| Predicate | managementIssues |
P17287
|
FINISHED |
| Object | wild horse management |
—
|
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: wild horse management | Statement: [Virginia Range, managementIssues, wild horse management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managementIssues Context triple: [Virginia Range, managementIssues, wild horse management]
-
A.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
B.
majorIssue
Indicates that something is a primary or most significant problem, concern, or obstacle in a given context.
-
C.
addressesIssue
Indicates that one entity deals with, responds to, or attempts to resolve a specific issue associated with another entity.
-
D.
issueType
chosen
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
E.
knownIssue
Indicates that the subject has an issue or problem that is already identified, recognized, or documented.
- 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_69a4948331fc8190b531ac9bec71c491 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be1d55a08190a138b2411a7c4376 |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.