Triple
T10114266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Forest Watch |
E218316
|
entity |
| Predicate | monitorsArea |
P752
|
FINISHED |
| Object | global forests |
—
|
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: global forests | Statement: [Global Forest Watch, monitorsArea, global forests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monitorsArea Context triple: [Global Forest Watch, monitorsArea, global forests]
-
A.
monitors
chosen
Indicates that one entity observes, tracks, or checks the state, behavior, or performance of another entity over time.
-
B.
typicalMonitor
Indicates that one entity commonly or characteristically monitors, observes, or oversees another entity in a usual or expected manner.
-
C.
areaCControl
Indicates that an entity exercises control or authority over a specific geographic area or region.
-
D.
areaAControl
Indicates that one entity exercises control or authority over a specified area or region.
-
E.
monitoringBody
Indicates that one entity is responsible for overseeing, supervising, or tracking the activities, performance, or compliance 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd15ffcd48190825800611aab2aab |
completed | April 2, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:04 p.m.