Triple
T28796988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senussi order |
E727110
|
entity |
| Predicate | providedRoyalFamilyOf |
P81631
|
FINISHED |
| Object | Kingdom of Libya |
—
|
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: Kingdom of Libya | Statement: [Senussi order, providedRoyalFamilyOf, Kingdom of Libya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedRoyalFamilyOf Context triple: [Senussi order, providedRoyalFamilyOf, Kingdom of Libya]
-
A.
royalTribe
Indicates that an entity belongs to, descends from, or is associated with a tribe that holds royal or ruling status.
-
B.
relatedRoyalHouse
Indicates a relationship where one royal house is historically, genealogically, or politically connected to another royal house.
-
C.
royalAssociation
chosen
Indicates a relationship in which an entity is connected or linked to royalty, a royal person, or a royal institution.
-
D.
managerOfRoyals
Indicates that one entity serves as the manager responsible for overseeing or directing the Royals.
-
E.
hasRoyalFamilyMember
Indicates that one entity is a member of the royal family associated with another entity.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 28, 2026, 6:25 a.m.