Triple
T38130131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Marcianople |
E952196
|
entity |
| Predicate | GothicLeader |
P85310
|
FINISHED |
| Object | Fritigern |
—
|
NE NERFINISHED |
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: Fritigern | Statement: [Battle of Marcianople, GothicLeader, Fritigern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GothicLeader Context triple: [Battle of Marcianople, GothicLeader, Fritigern]
-
A.
GothicCommander
chosen
Indicates a relationship where an entity holds the role or title of a commander within a Gothic context, such as a Gothic army, faction, or cultural group.
-
B.
Listoghil
Indicates a relationship in which an entity is associated with or belongs to the place or context referred to as Listoghil.
-
C.
ClarimondeRole
Indicates that one entity holds the specific narrative or functional role associated with Clarimonde in relation to another entity.
-
D.
Normgeber
Indicates that an entity serves as a norm-giver or authority that creates, issues, or establishes binding rules, standards, or regulations for others.
-
E.
GermanicLeader
Indicates that an entity serves as a leader or ruling figure within a Germanic group, tribe, or people.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.