Triple
T31063585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPCAT establishing resolution |
E791609
|
entity |
| Predicate | fallsUnderAgendaItem |
P170706
|
FINISHED |
| Object | human 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: human rights | Statement: [OPCAT establishing resolution, fallsUnderAgendaItem, human rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fallsUnderAgendaItem Context triple: [OPCAT establishing resolution, fallsUnderAgendaItem, human rights]
-
A.
fallContributedTo
Indicates that one event, condition, or factor played a role in causing or leading to a particular fall.
-
B.
fallsUnderChapter
Indicates that one item is categorized within, or governed by, a specific chapter of a larger document, code, or classification system.
-
C.
fallsUnderPart
Indicates that one entity is categorized as a specific part or component within a broader entity or grouping.
-
D.
issue
Indicates that an entity formally publishes, releases, or distributes something, such as a document, statement, or item, often in an official or authoritative capacity.
-
E.
fallStatus
Indicates the condition or outcome of a fall event affecting an entity.
- F. None of above. chosen
Provenance (4 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695792b748190882e715603d406a2 |
completed | May 3, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 29, 2026, 9:01 p.m.