Triple
T5174938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander the Liberator |
E116773
|
entity |
| Predicate | numberOfSerfsFreed |
P62169
|
FINISHED |
| Object | over 20 million |
—
|
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: over 20 million | Statement: [Alexander the Liberator, numberOfSerfsFreed, over 20 million]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSerfsFreed Context triple: [Alexander the Liberator, numberOfSerfsFreed, over 20 million]
-
A.
numberOfEnslaved
Indicates the quantity of individuals who were held in a state of enslavement in relation to a given entity or context.
-
B.
beneficiariesOfEmancipation
Indicates that the subject is a person or group who gains rights, freedoms, or advantages as a result of an emancipation event or process.
-
C.
wasFormerlyEnslaved
Indicates that an entity was previously held in a condition of slavery or bondage but is no longer enslaved.
-
D.
hasEnslavedCharacter
Indicates that one entity has held another entity in a state of slavery or forced servitude.
-
E.
liberationAchievedBy
Indicates that a state of liberation or freedom is brought about or attained through a specific action, process, or agent.
- 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7971284481909e6d07b2368a4f76 |
completed | March 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69bd77b529948190b86671ebe43f4734 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79251b548190918a1eb930e24c22 |
completed | March 20, 2026, 4:43 p.m. |
Created at: March 20, 2026, 1:45 p.m.