Triple
T37077199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Save-the-Redwoods League |
E917740
|
entity |
| Predicate | hasHelpedCreate |
P290
|
FINISHED |
| Object | redwood state parks |
—
|
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: redwood state parks | Statement: [Save-the-Redwoods League, hasHelpedCreate, redwood state parks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHelpedCreate Context triple: [Save-the-Redwoods League, hasHelpedCreate, redwood state parks]
-
A.
hasCreation
Indicates a relationship where one entity is the creator or originator of another entity.
-
B.
hasMade
Indicates that an entity has created, produced, or brought about another entity or outcome.
-
C.
hasCreationStatus
Indicates the current state or phase of existence or development that something is in, such as whether it is planned, in progress, completed, or otherwise defined in its lifecycle.
-
D.
helpedCause
Indicates that one entity contributed to bringing about, enabling, or facilitating an outcome or event involving another entity.
-
E.
supportedCreationOf
chosen
Indicates that one entity actively aided, endorsed, or facilitated the bringing into existence or establishment 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:14 p.m.