Triple
T34880457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dally Messenger |
E1005995
|
entity |
| Predicate | honourNamedAfter |
P18840
|
FINISHED |
| Object | Dally M Medal |
—
|
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: Dally M Medal | Statement: [Dally Messenger, honourNamedAfter, Dally M Medal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honourNamedAfter Context triple: [Dally Messenger, honourNamedAfter, Dally M Medal]
-
A.
namedInHonorBy
Indicates that one entity has been used as the namesake or dedicatee by another entity, signifying that the latter is named in honor of the former.
-
B.
fieldNamedInHonorOf
Indicates that a field (such as a sports or academic field) bears a particular name as a tribute or dedication to a specific person or entity.
-
C.
peopleNamedAfter
Indicates that one person or group received their name in honor of, or derived from, another person or group.
-
D.
alsoHonoredAs
Indicates that an entity is additionally recognized or celebrated under another title, role, or form of honor beyond its primary designation.
-
E.
hasAwardNamedAfter
chosen
Indicates that an entity has an award that is named in honor of another entity.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.