Triple
T7757790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cato |
E175940
|
entity |
| Predicate | numberOfParticipantsInRebellion |
P38158
|
FINISHED |
| Object | about 60 to 100 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: about 60 to 100 enslaved people | Statement: [Cato, numberOfParticipantsInRebellion, about 60 to 100 enslaved people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfParticipantsInRebellion Context triple: [Cato, numberOfParticipantsInRebellion, about 60 to 100 enslaved people]
-
A.
facedRebellionBy
Indicates that an entity experienced opposition or an uprising initiated by another entity.
-
B.
ageDuringRebellion
Indicates the age a person or entity was during the time of a specified rebellion.
-
C.
approximateRebelStrength
chosen
Indicates an estimation of the size or capability of rebel forces rather than an exact measured strength.
-
D.
typeOfRebel
Indicates that one entity is a rebel belonging to, or classified under, a particular type or category of rebellion.
-
E.
joinedRebellion
Indicates that an entity became a member or active participant in a rebellion against an established authority.
- 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_69c6996180088190832e38e8d83ff54a |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c705257ca08190a78c592a1e616da8 |
completed | March 27, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69c7016df2b08190b2330a2010691431 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:09 p.m.