Triple
T25456750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | صاحب رفادة الحاج |
E637933
|
entity |
| Predicate | زمن_المسؤولية |
P158560
|
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.
responsibleFor
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
-
B.
scopeOfDuty
Indicates the range or extent of responsibilities, tasks, or obligations that an entity is expected or authorized to perform.
-
C.
تحمله
Indicates that one entity carries, bears, or supports another entity physically, emotionally, or figuratively.
-
D.
accountabilityTo
Indicates that one entity is responsible for explaining, justifying, or answering for its actions, decisions, or outcomes to another entity.
-
E.
זמנם
Indicates a relationship involving the time allotted to, belonging to, or associated with certain entities (e.g., “their time”).
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f72756748190aa315cc00882a798 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:10 p.m.