Triple
T2771492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wheeze Kids |
E61465
|
entity |
| Predicate | nicknameCoincidesWith |
P28716
|
FINISHED |
| Object | Whiz Kids 1950 Phillies nickname |
—
|
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: Whiz Kids 1950 Phillies nickname | Statement: [Wheeze Kids, nicknameCoincidesWith, Whiz Kids 1950 Phillies nickname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameCoincidesWith Context triple: [Wheeze Kids, nicknameCoincidesWith, Whiz Kids 1950 Phillies nickname]
-
A.
nicknameEmphasizes
Indicates that a nickname highlights or draws special attention to a particular characteristic, trait, or aspect of the entity it refers to.
-
B.
isNickname
chosen
Indicates that one name is an informal or alternative name commonly used to refer to the same person or entity as another name.
-
C.
sharesGivenNameWith
Indicates that two entities have the same given (first) name.
-
D.
sharesSignsWith
Indicates that two entities exhibit the same or overlapping signs, symptoms, or observable indicators.
-
E.
coinedIn
Indicates that something (typically a term, phrase, or name) was first created or introduced at a particular time or in a particular place.
- 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdcfed608819080988e93df7bdf7c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.