Triple
T33116367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahl al-Shajarah |
E847467
|
entity |
| Predicate | pledgeContext |
P176119
|
FINISHED |
| Object | Treaty of Hudaybiyyah |
—
|
NE NERFINISHED |
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: Treaty of Hudaybiyyah | Statement: [Ahl al-Shajarah, pledgeContext, Treaty of Hudaybiyyah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pledgeContext Context triple: [Ahl al-Shajarah, pledgeContext, Treaty of Hudaybiyyah]
-
A.
pledgedBy
Indicates that a commitment, promise, or formal pledge was made by a specific entity.
-
B.
tookPledgeUnder
Indicates that one entity formally swore allegiance, loyalty, or commitment while under the authority, supervision, or auspices of another entity.
-
C.
usesPledge
Indicates that one entity employs or relies on a specific pledge, promise, or formal commitment in its actions or relationships with another entity.
-
D.
covenantContext
Indicates the situational, legal, or relational framework within which a covenant or binding agreement is made, interpreted, or applied.
-
E.
pledgedByOthers
Indicates that a commitment, promise, or pledge toward an entity is made by parties other than the primary or focal entity.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:27 a.m.