Triple
T38425171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajah Sulayman |
E903338
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Filipino noble |
C64698
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Filipino noble Context triple: [Rajah Sulayman, instanceOf, Filipino noble]
-
A.
Filipino ruler
chosen
A Filipino ruler is a sovereign or political leader who has held supreme authority over a territory or polity in the Philippine archipelago, whether as a precolonial datu, sultan, or rajah, or as a modern head of state or government.
-
B.
Leonese noble
A Leonese noble is a member of the hereditary aristocracy of the medieval Kingdom of León, holding land, titles, and political influence under the Leonese crown.
-
C.
Tongan noble
A Tongan noble is a hereditary or royally appointed member of Tonga’s traditional aristocracy who holds chiefly titles, land rights, and social authority within the kingdom’s hierarchical cultural and political system.
-
D.
Ryukyuan lord
A Ryukyuan lord was a regional noble of the Ryukyu Kingdom who governed local territories, managed tribute and trade, and served the royal court in a hierarchical feudal system influenced by both Japanese and Chinese cultures.
-
E.
Granadan noble
A Granadan noble is a high-ranking member of the aristocracy in the Emirate or Kingdom of Granada, distinguished by lineage, landownership, political influence, and often military or administrative roles within Granadan society.
- F. None of above.
Provenance (1 batch)
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_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.