Triple
T7993231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mass Audubon wildlife sanctuary network |
E186058
|
entity |
| Predicate | missionAlignedWith |
P8671
|
FINISHED |
| Object | nature conservation |
—
|
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: nature conservation | Statement: [Mass Audubon wildlife sanctuary network, missionAlignedWith, nature conservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionAlignedWith Context triple: [Mass Audubon wildlife sanctuary network, missionAlignedWith, nature conservation]
-
A.
missionStrategy
Indicates the overarching plan, approach, or method an entity adopts to achieve a specific mission or objective.
-
B.
missionFocus
chosen
Indicates that an entity’s primary attention, effort, or resources are directed toward a particular mission, goal, or objective.
-
C.
missionLed
Indicates that an entity served as the leader or commander of a particular mission.
-
D.
missionScope
Indicates the defined range, objectives, and boundaries within which a mission or operation is intended to be carried out.
-
E.
missionTo
Indicates that one entity is assigned, directed, or sent to carry out a specific mission involving another entity or location.
- 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_69ca829c6c308190ab05b43d234c52b2 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c729afc81909d477b1623ac3f9d |
completed | March 31, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:16 p.m.