Triple
T4040293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dar al-Harb |
E83928
|
entity |
| Predicate | sometimesCriticizedFor |
P53756
|
FINISHED |
| Object | binary view of world order |
—
|
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: binary view of world order | Statement: [Dar al-Harb, sometimesCriticizedFor, binary view of world order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesCriticizedFor Context triple: [Dar al-Harb, sometimesCriticizedFor, binary view of world order]
-
A.
criticizedFor
Indicates that one entity expresses disapproval or negative judgment of another entity specifically because of a particular action, quality, or outcome.
-
B.
hasCriticism
Indicates that one entity expresses disapproval, objection, or negative evaluation directed toward another entity.
-
C.
criticizedConstruct
Indicates that one entity expressed disapproval or negative judgment about another entity’s constructed work, idea, or creation.
-
D.
alsoCalledByCritics
Indicates that critics refer to the same entity by an alternative name or label.
-
E.
aimsToCritique
Indicates an intention to analyze and point out faults, limitations, or weaknesses in something.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb39400881909d0f5430f04e441c |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef98ed84c81909dc86097df4afd4f |
completed | March 9, 2026, 4:47 p.m. |
Created at: March 9, 2026, 3:37 p.m.