Triple
T796376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nēnē |
E17031
|
entity |
| Predicate | conservationSuccessStory |
P19128
|
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: [nēnē, conservationSuccessStory, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conservationSuccessStory Context triple: [nēnē, conservationSuccessStory, true]
-
A.
conservationFocus
Indicates that the primary emphasis or priority of an entity, project, or action is on conservation-related goals, activities, or outcomes.
-
B.
conservationIssue
Indicates that an entity is associated with a problem, threat, or concern related to the protection, preservation, or sustainable management of natural resources or biodiversity.
-
C.
conservationValue
Indicates the degree to which something is considered important or valuable for conservation or protection of natural or cultural resources.
-
D.
conservationTool
Indicates that an entity functions as a tool, method, or resource used to support or carry out conservation activities or objectives.
-
E.
conservationObligation
Indicates a duty or responsibility to protect, preserve, or sustainably manage a resource, environment, or entity.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7b172e88190a26d31c9075b81fb |
completed | March 1, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69a4a5122a008190b0c621b7bc588d41 |
completed | March 1, 2026, 8:44 p.m. |
| PDg | Predicate description generation | batch_69a4a5bed20c81909ecc28bf42594e72 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:38 p.m.