Triple
T17403016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolis, Illinois |
E423142
|
entity |
| Predicate | officialNickname |
P37280
|
FINISHED |
| Object | Hometown of Superman |
—
|
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: Hometown of Superman | Statement: [Metropolis, Illinois, officialNickname, Hometown of Superman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialNickname Context triple: [Metropolis, Illinois, officialNickname, Hometown of Superman]
-
A.
unofficialNickname
Indicates that one entity is informally or colloquially known by a non-official nickname represented by the other entity.
-
B.
isOfficialNicknameOf
chosen
Indicates that one name is the formally recognized nickname or informal moniker used to refer to another entity.
-
C.
notableTeamNickname
Indicates that a team is commonly known by a particular nickname that is notable or widely recognized.
-
D.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
E.
academyNickname
Indicates that an entity is known by a particular informal or colloquial nickname within an academy or academic institution context.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43b051cc48190872278ee0b52240d |
completed | April 19, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.