Triple
T17066905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Said dynasty |
E414110
|
entity |
| Predicate | splitOfRealm |
P62618
|
FINISHED |
| Object | 1861 partition between Oman and Zanzibar branches |
—
|
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: 1861 partition between Oman and Zanzibar branches | Statement: [Al Said dynasty, splitOfRealm, 1861 partition between Oman and Zanzibar branches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: splitOfRealm Context triple: [Al Said dynasty, splitOfRealm, 1861 partition between Oman and Zanzibar branches]
-
A.
factionSplit
Indicates that a previously unified group has divided into separate, often opposing, factions.
-
B.
dividedIn
Indicates that one entity is partitioned or separated into multiple distinct parts, sections, or groups represented by another entity.
-
C.
divisionSince
chosen
Indicates that one entity has been divided or split from another starting at a specific point in time.
-
D.
capitalDivision
Indicates that one administrative division serves as the capital of another administrative division or political entity.
-
E.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbbddd708190a6192466b7dfd606 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.