Triple
T9896939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Objectives Resolution |
E182198
|
entity |
| Predicate | protectsRightsOf |
P13930
|
FINISHED |
| Object | Muslims |
—
|
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: Muslims | Statement: [Objectives Resolution, protectsRightsOf, Muslims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectsRightsOf Context triple: [Objectives Resolution, protectsRightsOf, Muslims]
-
A.
protectsRight
chosen
Indicates that one entity safeguards, upholds, or defends the legal or moral rights of another entity.
-
B.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
C.
rightsProtectionMechanism
Indicates a mechanism or process through which an entity’s rights are safeguarded, enforced, or defended in relation to another entity or system.
-
D.
aimsToProtect
Indicates an intention or purpose to safeguard or defend one entity, value, or condition from harm, risk, or undesirable outcomes.
-
E.
legalProtectionFor
Indicates that one entity provides or is subject to legal safeguards, rights, or defenses in favor of another entity or interest.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4ab15f881909f75a8e01051dbc4 |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:40 p.m.