Triple
T4520712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mapocho Urbano Limpio project |
E103260
|
entity |
| Predicate | hasSocialGoal |
P17117
|
FINISHED |
| Object | enhance public access to the river |
—
|
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: enhance public access to the river | Statement: [Mapocho Urbano Limpio project, hasSocialGoal, enhance public access to the river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialGoal Context triple: [Mapocho Urbano Limpio project, hasSocialGoal, enhance public access to the river]
-
A.
philanthropicGoal
chosen
Indicates a relationship where an action, initiative, or entity is directed toward achieving a charitable or socially beneficial objective.
-
B.
hasPrimaryGoal
Indicates that an entity’s main or most important objective is the specified goal.
-
C.
hasCulturalGoal
Indicates that an entity is pursuing, oriented toward, or defined by a specific cultural objective or aspiration.
-
D.
supportGoal
Indicates that one entity actively helps, promotes, or contributes to the achievement of another entity’s goal.
-
E.
hasManagementGoal
Indicates that an entity is associated with a specific management objective or target it is intended to achieve or support.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5749d95481908db0176459c096cf |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.