Triple
T28007171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Qaʾim |
E707308
|
entity |
| Predicate | expectedAction |
P163619
|
FINISHED |
| Object | to fill the earth with justice |
—
|
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: to fill the earth with justice | Statement: [al-Qaʾim, expectedAction, to fill the earth with justice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedAction Context triple: [al-Qaʾim, expectedAction, to fill the earth with justice]
-
A.
expectedAction
chosen
Indicates that a particular action is anticipated or required to occur in a given context or scenario.
-
B.
requiredAction
Indicates that a specific action must be performed or fulfilled as a necessary condition in the given context.
-
C.
expectedValue
Indicates the predicted or average outcome of a variable or event, typically computed as a probability-weighted sum of all possible values.
-
D.
promptedAction
Indicates that one entity initiates or triggers another entity to perform a specific action.
-
E.
subsequentAction
Indicates that one action occurs after another in time, following it as a later step or consequence.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:01 p.m.