Triple
T37756397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhino |
E941124
|
entity |
| Predicate | introducedAsNicknameFor |
P38200
|
FINISHED |
| Object | F-4 Phantom II |
—
|
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: F-4 Phantom II | Statement: [Rhino, introducedAsNicknameFor, F-4 Phantom II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsNicknameFor Context triple: [Rhino, introducedAsNicknameFor, F-4 Phantom II]
-
A.
isOfficialNicknameOf
Indicates that one name is the formally recognized nickname or informal moniker used to refer to another entity.
-
B.
nicknamedFor
chosen
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
C.
dedicatedToOrNicknameOf
Indicates that one entity is either the dedicatee of something (e.g., a work, object, or honor) or serves as an alternative name or nickname for another entity.
-
D.
replacedNicknameOf
Indicates that one nickname has been superseded or substituted by another nickname for the same entity.
-
E.
usedAsNicknameSince
Indicates that one entity has been used as a nickname for another entity starting from a specified point in time.
- 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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: May 3, 2026, 4:19 p.m.