Triple
T37612211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngiwal Village |
E935813
|
entity |
| Predicate | hasAccessToForestResources |
P193165
|
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: [Ngiwal Village, hasAccessToForestResources, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessToForestResources Context triple: [Ngiwal Village, hasAccessToForestResources, true]
-
A.
hasForestAssociation
Indicates an ecological or contextual relationship in which an entity is associated with, influenced by, or characteristically occurs in forest environments.
-
B.
hasAccessToMarineResources
Indicates that one entity is able to use, exploit, or otherwise benefit from marine resources controlled by another entity or area.
-
C.
hasForestType
Indicates that an area or location is characterized by a specific type or classification of forest.
-
D.
hasForestProduce
Indicates that one entity possesses, yields, or is a source of forest-derived products or resources for another.
-
E.
hasNationalForest
Indicates that a place or jurisdiction contains, includes, or is home to at least one designated national forest.
- F. None of above. chosen
Provenance (4 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: May 3, 2026, 4:18 p.m.