Triple
T28410358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Germania |
E719645
|
entity |
| Predicate | notableTribeOpponents |
P156489
|
FINISHED |
| Object | Cherusci |
—
|
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: Cherusci | Statement: [Roman Germania, notableTribeOpponents, Cherusci]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTribeOpponents Context triple: [Roman Germania, notableTribeOpponents, Cherusci]
-
A.
notableCompetitorPairs
Indicates that the two entities form a pair of organizations or individuals that are notably recognized as competitors with each other.
-
B.
notableRivalOpponent
chosen
Indicates that one entity is a particularly significant or well-known rival or opponent of another entity.
-
C.
notableRivalTeam
Indicates that one team is recognized as a significant or well-known rival of another team.
-
D.
notableOpponentTeamMember
Indicates that a specific team member is recognized as a particularly significant or noteworthy opponent in relation to another entity or context.
-
E.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a00d820a7788190a8d54625cd87be68 |
completed | May 10, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_6a00d7c5b40c8190b80413238d04e81e |
completed | May 10, 2026, 7:08 p.m. |
Created at: April 28, 2026, 1:26 a.m.