Triple
T37887104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neuer |
E945025
|
entity |
| Predicate | hasFamousAssociationWith |
P197651
|
FINISHED |
| Object | football |
—
|
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: football | Statement: [Neuer, hasFamousAssociationWith, football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamousAssociationWith Context triple: [Neuer, hasFamousAssociationWith, football]
-
A.
isBorneByNotablePeopleIn
Indicates that something (such as a name, title, or attribute) is carried or held by notable people within a specified place or context.
-
B.
notableBuildingAssociated
Indicates a relationship where a notable or significant building is associated with, connected to, or relevant to a given entity.
-
C.
notoriouslyAssociatedWith
Indicates a widely recognized and often negative or infamous association between one entity and another.
-
D.
hasProminentPlaceOn
Indicates that one entity occupies a highly visible, important, or emphasized position on another entity (such as a surface, list, or layout).
-
E.
hasNearbyNotablePersonAssociation
Indicates a relationship where an entity is associated with a notable person who is located nearby or in close geographic proximity.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
| PDg | Predicate description generation | batch_69fe9fb88db08190a8f4af350633330e |
completed | May 9, 2026, 2:45 a.m. |
Created at: May 3, 2026, 4:19 p.m.