Triple
T33604467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Grassland |
E860809
|
entity |
| Predicate | adminAgencyType |
P172038
|
FINISHED |
| Object | federal land management agency |
—
|
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: federal land management agency | Statement: [National Grassland, adminAgencyType, federal land management agency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adminAgencyType Context triple: [National Grassland, adminAgencyType, federal land management agency]
-
A.
isAgencyType
chosen
Indicates that an entity belongs to, or is classified under, a particular type or category of agency.
-
B.
agencyRenamedFrom
Indicates that an agency currently known by one name was previously known by another name.
-
C.
agencyTypeCreated
Indicates that a specific type or category of agency has been created or established.
-
D.
customerAgency
Indicates a relationship where one party (the customer) authorizes or is represented by another party (the agency) to act on their behalf in transactions or decisions.
-
E.
isAgencyFor
Indicates that one entity functions as an agent or representative acting on behalf 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:41 a.m.