Triple
T24579625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maldini football family |
E608211
|
entity |
| Predicate | clubLegacy |
P128466
|
FINISHED |
| Object | AC Milan defensive icons |
—
|
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: AC Milan defensive icons | Statement: [Maldini football family, clubLegacy, AC Milan defensive icons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubLegacy Context triple: [Maldini football family, clubLegacy, AC Milan defensive icons]
-
A.
legacyForClub
chosen
Indicates that an entity has left a lasting impact, tradition, or enduring contribution associated with a particular club.
-
B.
clubLegendOf
Indicates that a person is widely regarded as a legendary or iconic figure for a particular club, typically due to exceptional contribution or long-term impact.
-
C.
clubHonour
Indicates that a club has received or been awarded a particular honour, title, or distinction.
-
D.
clubPredecessorOf
Indicates that one club existed earlier and was replaced or succeeded by another club in an organizational or historical sequence.
-
E.
clubBase
Indicates the location or place that serves as the primary base or home venue for a club.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a97fde9c81909d8de91b6358a015 |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.