Triple
T25355899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Leahy |
E635818
|
entity |
| Predicate | hasNameInstance |
P164167
|
FINISHED |
| Object | Tom Leahy (Australian footballer) |
—
|
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: Tom Leahy (Australian footballer) | Statement: [Tom Leahy, hasNameInstance, Tom Leahy (Australian footballer)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInstance Context triple: [Tom Leahy, hasNameInstance, Tom Leahy (Australian footballer)]
-
A.
hasNameCharacteristic
Indicates that an entity possesses a specific quality or attribute related to its name.
-
B.
hasNameFunction
Indicates that an entity is associated with a function whose purpose is to provide or determine its name.
-
C.
hasNameString
Indicates that an entity is associated with a specific textual string used as its name.
-
D.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
E.
hasNameInIAST
Indicates that an entity is associated with a specific name written in the International Alphabet of Sanskrit Transliteration (IAST) system.
- F. None of above. chosen
Provenance (4 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f643c204508190a43fe0ec5165b01c |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 21, 2026, 1:36 p.m.