Triple
T13897293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baptist War |
E334120
|
entity |
| Predicate | hasEstimatedParticipants |
P111137
|
FINISHED |
| Object | around 60,000 enslaved people |
—
|
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: around 60,000 enslaved people | Statement: [Baptist War, hasEstimatedParticipants, around 60,000 enslaved people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstimatedParticipants Context triple: [Baptist War, hasEstimatedParticipants, around 60,000 enslaved people]
-
A.
numberOfParticipants
Indicates the total count of entities involved in a particular event, activity, or relationship.
-
B.
hasApproximateNumberOfPeople
chosen
Indicates that an entity is associated with an estimated or approximate count of people, rather than an exact number.
-
C.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
D.
approximateAudienceSize
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
-
E.
hasApproximateTotalSpeakers
Indicates that an entity is associated with an estimated or roughly calculated number of total speakers, rather than an exact count.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de25d72c6c819093bf9c43136839d4 |
completed | April 14, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.