Triple
T33116416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People of Ridwan |
E847468
|
entity |
| Predicate | typeOfPledge |
P164818
|
FINISHED |
| Object | 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: oath of allegiance | Statement: [People of Ridwan, typeOfPledge, oath of allegiance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPledge Context triple: [People of Ridwan, typeOfPledge, oath of allegiance]
-
A.
philanthropicPledge
Indicates a commitment by an entity to donate resources, typically money or assets, for charitable or public-benefit purposes.
-
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.
pledgedBy
Indicates that a commitment, promise, or formal pledge was made by a specific entity.
-
D.
reasonForPledge
Indicates the motivation or justification behind making a particular pledge or commitment.
-
E.
dedicationType
Indicates the specific kind or category of dedication that characterizes the relationship or action between entities.
- 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_6a00a094c44c81908e4501151688a635 |
completed | May 10, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_6a009fcdfd848190841deaad9667d347 |
completed | May 10, 2026, 3:10 p.m. |
Created at: May 1, 2026, 1:27 a.m.