Triple
T34604123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metaurus |
E888547
|
entity |
| Predicate | battleCommanderRoman |
P48696
|
FINISHED |
| Object | Gaius Claudius Nero |
—
|
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: Gaius Claudius Nero | Statement: [Metaurus, battleCommanderRoman, Gaius Claudius Nero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleCommanderRoman Context triple: [Metaurus, battleCommanderRoman, Gaius Claudius Nero]
-
A.
RomanCommander
chosen
Indicates a relationship where an entity holds the role or position of a commander within a Roman military or organizational context.
-
B.
NumidianCommander
Indicates that an entity serves as a military commander associated with Numidia or Numidian forces.
-
C.
SamniteCommander
Indicates that one entity serves as a military commander or leader within the Samnite forces or context.
-
D.
ByzantineCommander
Indicates a relationship where an entity holds the role or function of a commander within a Byzantine military or organizational context.
-
E.
GallicCommander
Indicates a person who holds a commanding or leadership role over Gallic forces or within a Gallic 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:03 a.m.