Triple
T30354910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | غار ثور |
E772116
|
entity |
| Predicate | eventHappenedHere |
P165186
|
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: [غار ثور, eventHappenedHere, اختباء النبي محمد وأبي بكر الصديق من قريش]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventHappenedHere Context triple: [غار ثور, eventHappenedHere, اختباء النبي محمد وأبي بكر الصديق من قريش]
-
A.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
B.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
-
C.
tookPlaceAtEvent
Indicates that an action or occurrence happened during or in the context of a specific event.
-
D.
tookPlaceAtLocation
chosen
Indicates that an event or action occurred at a specific location.
-
E.
hadEvent
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 7:56 p.m.