Triple
T8688204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max-Morlock-Stadion |
E206217
|
entity |
| Predicate | namedAfterOccupationOfNamesake |
P63
|
FINISHED |
| Object | German footballer |
—
|
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: German footballer | Statement: [Max-Morlock-Stadion, namedAfterOccupationOfNamesake, German footballer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterOccupationOfNamesake Context triple: [Max-Morlock-Stadion, namedAfterOccupationOfNamesake, German footballer]
-
A.
isNamedAfterOccupation
Indicates that an entity’s name is derived from or based on a particular occupation or profession.
-
B.
namesakeOccupation
Indicates that one entity’s occupation is the same as, or derived from, the occupation associated with the other entity’s namesake.
-
C.
namedAfter
chosen
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
D.
successorNamesake
Indicates that one entity is named after another entity that precedes it, typically as its successor or continuation in name.
-
E.
hadEponymousAncestor
Indicates that an entity has an ancestor whose name it shares or from whom its own name is derived.
- 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5731cf08819082e0cbe0975b70bb |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.