Triple
T30886172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julius Bassianus |
E786771
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Syrian aristocrat |
C46651
|
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: Syrian aristocrat Context triple: [Julius Bassianus, instanceOf, Syrian aristocrat]
-
A.
Lebanese aristocrat
A Lebanese aristocrat is a member of Lebanon’s traditional upper class, typically linked to historic landowning or political families, who embodies refined social status, cultural sophistication, and influence within Lebanese society.
-
B.
Arab noble
chosen
An Arab noble is a member of the traditional aristocratic or ruling elite in Arab societies, typically distinguished by lineage, social status, and historical roles in governance, leadership, or landownership.
-
C.
Greek aristocrat
A Greek aristocrat is a wealthy, high-status individual from ancient or modern Greece, typically belonging to a privileged landowning or politically influential family and embodying traditional cultural refinement and social power.
-
D.
Arab noblewoman
An Arab noblewoman is a high-status woman of Arab heritage, often belonging to a historically influential family or lineage, who embodies cultural refinement, social responsibility, and traditional or contemporary forms of leadership within her community.
-
E.
Syrian political dynasty
A Syrian political dynasty is a family-based power structure in Syria in which political authority, leadership roles, and state influence are concentrated and passed down across generations within the same lineage.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:49 p.m.