Triple
T27271858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curtiss XP-55 Ascender |
E688073
|
entity |
| Predicate | humorousNickname |
P18159
|
FINISHED |
| Object | Ass-ender |
—
|
NE NERFINISHED |
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: Ass-ender | Statement: [Curtiss XP-55 Ascender, humorousNickname, Ass-ender]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humorousNickname Context triple: [Curtiss XP-55 Ascender, humorousNickname, Ass-ender]
-
A.
namePunOn
chosen
Indicates that one entity’s name is a play on, parody of, or humorous variation of another entity’s name.
-
B.
unofficialNickname
Indicates that one entity is informally or colloquially known by a non-official nickname represented by the other entity.
-
C.
hasAffectionateNicknameFor
Indicates that one entity uses or assigns a fond, affectionate, or endearing nickname to another entity.
-
D.
childhoodNickname
Indicates that one entity is a nickname that was used to refer to the other entity during their childhood.
-
E.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f62724de008190a38d2843e25b4d62 |
completed | May 2, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 10:59 a.m.