Triple
T33377779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Caecilius Metellus Dalmaticus |
E854681
|
entity |
| Predicate | tribe defeated |
P174565
|
FINISHED |
| Object | Dalmatae |
—
|
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: Dalmatae | Statement: [Lucius Caecilius Metellus Dalmaticus, tribe defeated, Dalmatae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribe defeated Context triple: [Lucius Caecilius Metellus Dalmaticus, tribe defeated, Dalmatae]
-
A.
tribeDefeated
chosen
Indicates that one tribe has overcome and defeated another tribe in a conflict or competition.
-
B.
sideDefeated
Indicates that one side in a conflict, competition, or contest has been beaten or overcome by another side.
-
C.
largerForceDefeated
Indicates that in a conflict or contest, the side with the numerically or materially larger force was ultimately defeated by its opponent.
-
D.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
E.
significantDefeat
Indicates that one entity has decisively and substantially defeated another, implying a clear and impactful victory rather than a narrow or marginal one.
- 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6dfff88848190833cb929eab3c818 |
completed | May 3, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69f6de0c821c8190ae3ebda9dfdd0064 |
completed | May 3, 2026, 5:33 a.m. |
Created at: May 1, 2026, 1:35 a.m.