Triple
T14922196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adirondack Forest Preserve (within town boundaries) |
E371541
|
entity |
| Predicate | hasProtectionFrom |
P38210
|
FINISHED |
| Object | development |
—
|
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: development | Statement: [Adirondack Forest Preserve (within town boundaries), hasProtectionFrom, development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtectionFrom Context triple: [Adirondack Forest Preserve (within town boundaries), hasProtectionFrom, development]
-
A.
providesProtectionIn
Indicates that one entity offers protection or safeguarding to another entity within a specified context, location, or situation.
-
B.
providesProtectionAgainst
Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
-
C.
isProtectedFrom
chosen
Indicates that one entity is safeguarded or shielded against harm, damage, or adverse effects caused by another entity or factor.
-
D.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
E.
isProtectedBy
Indicates that one entity provides protection, defense, or safeguarding for 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded63121e48190b54eb2546acc3c93 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:34 a.m.