Triple
T16475497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sustainable Development Goal 8 |
E400175
|
entity |
| Predicate | target8.8Focus |
P860
|
FINISHED |
| Object | protect labour rights |
—
|
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: protect labour rights | Statement: [Sustainable Development Goal 8, target8.8Focus, protect labour rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: target8.8Focus Context triple: [Sustainable Development Goal 8, target8.8Focus, protect labour rights]
-
A.
target
chosen
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
B.
targetWork
Indicates that one entity is the specific work (e.g., document, artwork, or project) that another entity is directed at, refers to, or is primarily concerned with.
-
C.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
D.
primaryTarget
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
-
E.
targetArea
Indicates the specific area or region that is the intended focus or destination of an action or effect.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32dd43cf88190881a5cbc80da1490 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.