Triple
T1053685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bugis |
E22753
|
entity |
| Predicate | traditionalSocialClass |
P22943
|
FINISHED |
| Object | aristocracy |
—
|
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: aristocracy | Statement: [Bugis, traditionalSocialClass, aristocracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalSocialClass Context triple: [Bugis, traditionalSocialClass, aristocracy]
-
A.
middleClass
Indicates that an entity belongs to the socioeconomic group characterized as the middle class.
-
B.
socialClassSystem
Indicates a hierarchical organization of people into social classes based on status, power, or economic position.
-
C.
traditionalCapital
Indicates that a location serves as the customary or historically recognized capital of a region, people, or polity, regardless of its current official capital status.
-
D.
commonerClass
Indicates that an entity belongs to the social or economic class of commoners, as opposed to nobility or other privileged groups.
-
E.
traditionalStatus
Indicates that one entity holds a customary, long-established, or culturally recognized role, condition, or standing in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8d669448190955507e2e4975b9f |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b731e25c8190b5ea8466648c2c9a |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7da38888190a118ef20ce4ae9aa |
completed | March 1, 2026, 10:04 p.m. |
Created at: March 1, 2026, 7:42 p.m.