Triple
T15974581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manager of the Century |
E387410
|
entity |
| Predicate | hasSuperlativeSense |
P2410
|
FINISHED |
| Object | best manager of the 20th century |
—
|
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: best manager of the 20th century | Statement: [Manager of the Century, hasSuperlativeSense, best manager of the 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuperlativeSense Context triple: [Manager of the Century, hasSuperlativeSense, best manager of the 20th century]
-
A.
superlative
chosen
Indicates that one entity possesses a property to the greatest or least degree when compared with all others in a given set.
-
B.
superior
Indicates that one entity holds a higher rank, status, or level of authority than another entity.
-
C.
hasTopness
Indicates that an entity possesses the quantum property of topness, typically associated with the presence or contribution of a top quark.
-
D.
moreExpressiveThan
Indicates that one entity conveys ideas, emotions, or information with greater richness, nuance, or clarity than another.
-
E.
morePrestigiousThan
Indicates that one entity is regarded as having higher status, esteem, or prestige than another.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.