Triple
T21807076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaius Duilius |
E538376
|
entity |
| Predicate | receivedHonorFor |
P15675
|
FINISHED |
| Object | victory at the Battle of Mylae |
—
|
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 at the Battle of Mylae | Statement: [Gaius Duilius, receivedHonorFor, victory at the Battle of Mylae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedHonorFor Context triple: [Gaius Duilius, receivedHonorFor, victory at the Battle of Mylae]
-
A.
awardReceived
Indicates that an entity has been granted or honored with a specific award or recognition.
-
B.
awardReceivedWith
Indicates that an entity received a specific award, optionally together with additional contextual details such as the work, role, or circumstances associated with that award.
-
C.
hasNotableHonor
Indicates that an entity has received a significant award, title, or formal recognition of distinction.
-
D.
recipientOfAward
Indicates that an entity has received or been granted a particular award.
-
E.
honoredThrough
chosen
Indicates that one entity is recognized or commemorated by means of another entity, event, or action.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07803b4888190af06bf7a90198f60 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.