Triple
T16341979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander II of Macedon |
E396827
|
entity |
| Predicate | relationToAlexanderTheGreat |
P10260
|
FINISHED |
| Object | paternal uncle |
—
|
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: paternal uncle | Statement: [Alexander II of Macedon, relationToAlexanderTheGreat, paternal uncle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToAlexanderTheGreat Context triple: [Alexander II of Macedon, relationToAlexanderTheGreat, paternal uncle]
-
A.
relativePositionToAlexanderIII
Indicates the spatial or hierarchical position of an entity in relation to Alexander III.
-
B.
relatesToAncientCity
Indicates a relationship or connection between an entity and an ancient city, such as origin, location, influence, or relevance.
-
C.
associatedWithAncientEmpire
Indicates that one entity has a historical, cultural, political, or geographic connection or affiliation with an ancient empire.
-
D.
roleInAlexiad
Indicates that one entity has a specific role or function within the context of the Alexiad (e.g., as an author, subject, or referenced figure).
-
E.
historicalRelationship
chosen
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da0ad510819082e440f5e2bceada |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.