Triple
T3478057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osceola National Forest (part) |
E73421
|
entity |
| Predicate | isFederallyManaged |
P23390
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Osceola National Forest (part), isFederallyManaged, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFederallyManaged Context triple: [Osceola National Forest (part), isFederallyManaged, true]
-
A.
canBeFederalizedBy
Indicates that an entity has the legal or practical capacity to be brought under the authority, control, or jurisdiction of a specified federal-level entity.
-
B.
federalStatus
chosen
Indicates that an entity holds a particular legal or administrative status under federal (national) authority or jurisdiction.
-
C.
isManagedFor
Indicates that one entity is administered, overseen, or controlled on behalf of another entity or purpose.
-
D.
federalSchemeImplemented
Indicates that a specific federal government program or policy has been put into operation or carried out in practice.
-
E.
containsFederalSubject
Indicates that one administrative or territorial entity includes a specific federal subject within its jurisdiction or boundaries.
- 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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb5b7584819096eadd1c5268eab1 |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.