Triple
T3355881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Reforestation Areas |
E70603
|
entity |
| Predicate | resourceManaged |
P10922
|
FINISHED |
| Object | timber |
—
|
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: timber | Statement: [New York State Reforestation Areas, resourceManaged, timber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceManaged Context triple: [New York State Reforestation Areas, resourceManaged, timber]
-
A.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
B.
resourceExtracted
chosen
Indicates that a resource has been obtained or taken from a source entity, typically through an extraction process.
-
C.
isManagedFor
Indicates that one entity is administered, overseen, or controlled on behalf of another entity or purpose.
-
D.
managedAs
Indicates that one entity is administered, controlled, or handled in the same way or under the same policies, procedures, or classification as another entity.
-
E.
riskManagedBy
Indicates that the potential or identified risk is controlled, mitigated, or overseen through the actions, policies, or responsibilities of a specified managing 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb242d4988190bbac993df587936d |
completed | March 8, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69ada42fbe7c8190b9f185b5ab985f17 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.