Triple
T3554056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles River |
E75176
|
entity |
| Predicate | hasRestorationGoal |
P45567
|
FINISHED |
| Object | improve habitat connectivity |
—
|
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: improve habitat connectivity | Statement: [Los Angeles River, hasRestorationGoal, improve habitat connectivity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRestorationGoal Context triple: [Los Angeles River, hasRestorationGoal, improve habitat connectivity]
-
A.
hasRestoration
Indicates that an entity has undergone, is undergoing, or is associated with a process of repair, renewal, or restoration.
-
B.
restorationGoal
chosen
Indicates that an action or plan is intended to return something to a previous, original, or improved state or condition.
-
C.
hasRestorationActivities
Indicates that an entity carries out, is involved in, or is associated with actions aimed at restoring or rehabilitating another entity or resource.
-
D.
hasRestorationFocus
Indicates that something is primarily concerned with or directed toward restoration or repair.
-
E.
hasConservationGoal
Indicates that an entity is associated with or aims to achieve a specific conservation-related objective or target.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc05549d88190acdebdd542ea1a67 |
completed | March 8, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:20 p.m.