Triple
T5174946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander the Liberator |
E116773
|
entity |
| Predicate | epithetReason |
P9593
|
FINISHED |
| Object | liberation of the serfs in 1861 |
—
|
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: liberation of the serfs in 1861 | Statement: [Alexander the Liberator, epithetReason, liberation of the serfs in 1861]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epithetReason Context triple: [Alexander the Liberator, epithetReason, liberation of the serfs in 1861]
-
A.
reasonForEpithet
chosen
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
B.
epithetOrTitle
Indicates that one entity serves as an epithet, honorific, or formal title used to designate or characterize another entity.
-
C.
languageOfEpithet
Indicates the language in which an epithet (such as a descriptive or honorary title) is expressed.
-
D.
reasonForHonorific
Indicates the reason, justification, or basis for which an honorific title or form of address is granted to or used for an entity.
-
E.
reasonForName
Indicates the explanation or cause behind why an entity has a particular name.
- 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_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. |
Created at: March 20, 2026, 1:45 p.m.