Triple
T33377776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Caecilius Metellus Dalmaticus |
E854681
|
entity |
| Predicate | reason for agnomen |
P9593
|
FINISHED |
| Object | victory in Dalmatia |
—
|
LITERAL FINISHED |
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: victory in Dalmatia | Statement: [Lucius Caecilius Metellus Dalmaticus, reason for agnomen, victory in Dalmatia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reason for agnomen Context triple: [Lucius Caecilius Metellus Dalmaticus, reason for agnomen, victory in Dalmatia]
-
A.
reasonForEpithet
chosen
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
B.
reasonForName
Indicates the explanation or cause behind why an entity has a particular name.
-
C.
reasonForHonorific
Indicates the reason, justification, or basis for which an honorific title or form of address is granted to or used for an entity.
-
D.
cognomenOf
Indicates that one entity is the cognomen (surname or family name) of another entity.
-
E.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
- 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_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 1, 2026, 1:35 a.m.