Triple
T32348562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Guard |
E826531
|
entity |
| Predicate | socialStatusAtFormation |
P171450
|
FINISHED |
| Object | enslaved soldiers |
—
|
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: enslaved soldiers | Statement: [Black Guard, socialStatusAtFormation, enslaved soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialStatusAtFormation Context triple: [Black Guard, socialStatusAtFormation, enslaved soldiers]
-
A.
socialStatusOrigin
chosen
Indicates the source or basis from which an entity’s social status is derived or determined.
-
B.
subjectSocialStatus
Indicates the social standing or rank that the subject holds within a society or group.
-
C.
statusInCommunity
Indicates the social standing, role, or level of acceptance an entity holds within a particular community.
-
D.
possibleSocialStatus
Indicates that one entity may hold, attain, or be associated with a particular social status in relation to another context or system.
-
E.
socialCondition
Indicates the social or societal circumstances, status, or environment affecting an entity at a given time.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 12:49 a.m.