Triple
T33116435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People of Ridwan |
E847468
|
entity |
| Predicate | tookPledgeUnder |
P175595
|
FINISHED |
| Object | a tree at Hudaybiyyah |
—
|
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: a tree at Hudaybiyyah | Statement: [People of Ridwan, tookPledgeUnder, a tree at Hudaybiyyah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookPledgeUnder Context triple: [People of Ridwan, tookPledgeUnder, a tree at Hudaybiyyah]
-
A.
swornInOn
Indicates that an individual formally assumes an office, role, or duty by taking an official oath on a specified date, occasion, or object.
-
B.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to 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.
pledgedBy
Indicates that a commitment, promise, or formal pledge was made by a specific entity.
-
E.
oathTakenBy
Indicates that an oath or formal promise has been made by a specific 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_69f6d6ee6e2081909c55bf6b31356d61 |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d30b9e048190b0982e30b7fdfa3c |
completed | May 3, 2026, 4:46 a.m. |
Created at: May 1, 2026, 1:27 a.m.