Triple
T15801318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | دلالة الحائرين |
E383103
|
entity |
| Predicate | مستهدف |
P860
|
FINISHED |
| Object | اليهود المتحيّرون بين الفلسفة والدين |
—
|
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: اليهود المتحيّرون بين الفلسفة والدين | Statement: [دلالة الحائرين, مستهدف, اليهود المتحيّرون بين الفلسفة والدين]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: مستهدف Context triple: [دلالة الحائرين, مستهدف, اليهود المتحيّرون بين الفلسفة والدين]
-
A.
target
chosen
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
B.
aimedAtBy
Indicates that one entity serves as the target or goal toward which another entity directs an action, intention, or focus.
-
C.
targetedForce
Indicates a deliberate application of force directed at a specific target or entity.
-
D.
aimsToCapture
Indicates an intention or effort by one entity to take control of, seize, or gain possession of another entity.
-
E.
victoryTarget
Indicates that one entity is the intended opponent, objective, or condition that must be overcome or achieved for the other entity to attain victory.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b522a2988190b2a2bde2da31b21e |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:48 a.m.