Triple
T29103634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teutobod |
E736703
|
entity |
| Predicate | enemyInConflict |
P117522
|
FINISHED |
| Object | Roman Republic |
—
|
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: Roman Republic | Statement: [Teutobod, enemyInConflict, Roman Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enemyInConflict Context triple: [Teutobod, enemyInConflict, Roman Republic]
-
A.
archenemyOf
Indicates a relationship in which one entity is the principal or most important enemy of another, often characterized by deep, ongoing opposition or rivalry.
-
B.
enemyDuringWar
Indicates that one entity is an enemy of another specifically in the context of a particular war or armed conflict.
-
C.
warAdversary
chosen
Indicates that two entities are opponents or enemies engaged in a state of war or armed conflict.
-
D.
allyInConflict
Indicates that one entity supports and cooperates with another entity as an ally within the context of a specific conflict or dispute.
-
E.
enemyNation
Indicates that one nation is considered a hostile or adversarial state in relation to another nation.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 11:14 a.m.