Triple
T18925399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Target 5.3 |
E462959
|
entity |
| Predicate | belongsToGoal |
P120603
|
FINISHED |
| Object | Gender equality |
—
|
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: Gender equality | Statement: [Target 5.3, belongsToGoal, Gender equality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToGoal Context triple: [Target 5.3, belongsToGoal, Gender equality]
-
A.
goalAssociatedWith
chosen
Indicates that a goal is connected or linked to another entity, such as an activity, plan, or outcome, in a way that reflects relevance or influence.
-
B.
statedAsGoalFor
Indicates that something has been explicitly declared or identified as a goal for a particular entity or context.
-
C.
allegedGoal
Indicates that one entity is claimed or reported to have the goal or intended objective of another entity, without asserting that the goal is actually true.
-
D.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
E.
supportsGoalType
Indicates that one entity is compatible with, or designed to facilitate, a particular type or category of goal.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9b94e008190a0e9a70aaf6d18ed |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:59 a.m.