Triple
T33116366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahl al-Shajarah |
E847467
|
entity |
| Predicate | pledgeType |
P164818
|
FINISHED |
| Object | bayʿah (oath of allegiance) |
—
|
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: bayʿah (oath of allegiance) | Statement: [Ahl al-Shajarah, pledgeType, bayʿah (oath of allegiance)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pledgeType Context triple: [Ahl al-Shajarah, pledgeType, bayʿah (oath of allegiance)]
-
A.
pledgedBy
Indicates that a commitment, promise, or formal pledge was made by a specific entity.
-
B.
usesPledge
chosen
Indicates that one entity employs or relies on a specific pledge, promise, or formal commitment in its actions or relationships with another entity.
-
C.
pledgedByOthers
Indicates that a commitment, promise, or pledge toward an entity is made by parties other than the primary or focal entity.
-
D.
dedicationType
Indicates the specific kind or category of dedication that characterizes the relationship or action between entities.
-
E.
pledgedAsCollateral
Indicates that one entity has been offered or assigned as security to guarantee the obligations or repayment of another.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6ee6e2081909c55bf6b31356d61 |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.