Triple
T1322207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam civic guard |
E28243
|
entity |
| Predicate | socialClassOfMembers |
P22943
|
FINISHED |
| Object | burgher class |
—
|
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: burgher class | Statement: [Amsterdam civic guard, socialClassOfMembers, burgher class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialClassOfMembers Context triple: [Amsterdam civic guard, socialClassOfMembers, burgher class]
-
A.
socialClassSystem
Indicates a hierarchical organization of people into social classes based on status, power, or economic position.
-
B.
socialClassAtBirth
Indicates the social class or socioeconomic status into which an individual was born.
-
C.
socialClassRepresented
Indicates that one entity portrays, embodies, or stands in for the social class or socioeconomic group associated with another entity.
-
D.
dominantSocialClass
Indicates that one social class holds primary power, influence, or status over others within a given social structure or context.
-
E.
traditionalSocialClass
chosen
Indicates that an entity belongs to or is associated with a particular traditional social class within a social hierarchy.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c19b76b48190aa8857b80971a842 |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beedb49c8190beb5b85cdda05013 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.