Triple
T9512645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M’Baku |
E229437
|
entity |
| Predicate | relationshipToRoyalFamily |
P917
|
FINISHED |
| Object | rival turned ally |
—
|
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: rival turned ally | Statement: [M’Baku, relationshipToRoyalFamily, rival turned ally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToRoyalFamily Context triple: [M’Baku, relationshipToRoyalFamily, rival turned ally]
-
A.
hasRoyalConnection
chosen
Indicates a relationship where an entity is linked or associated in some notable way to royalty, a royal family, or a royal institution.
-
B.
hasRoyalFamilyMember
Indicates that one entity is a member of the royal family associated with another entity.
-
C.
positionInRoyalFamily
Indicates the familial rank or role an individual holds within a royal family hierarchy.
-
D.
relatedRoyalHouse
Indicates a relationship where one royal house is historically, genealogically, or politically connected to another royal house.
-
E.
parentOfRoyalDescendants
Indicates being the parent of one or more individuals who are of royal descent.
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd986aa99c8190b2eaa7f9b111aa2e |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:58 p.m.