Triple
T8968915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Arthurs |
E214211
|
entity |
| Predicate | hairStyleOriginOfNickname |
P7596
|
FINISHED |
| Object | shaved head (Bonehead) |
—
|
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: shaved head (Bonehead) | Statement: [Paul Arthurs, hairStyleOriginOfNickname, shaved head (Bonehead)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hairStyleOriginOfNickname Context triple: [Paul Arthurs, hairStyleOriginOfNickname, shaved head (Bonehead)]
-
A.
reasonForNickname
chosen
Indicates the explanation or cause behind why a particular nickname was given to an entity.
-
B.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
C.
nameEtymologyFor
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
-
D.
mediaNicknameOrigin
Indicates that a media-related nickname originates from, or is derived based on, a particular source or context.
-
E.
aircraftNicknameOrigin
Indicates the source or reason from which an aircraft’s nickname is derived.
- 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_69ca839dbf608190a2f5990477115d29 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6764aca48190a5e472d1b6841886 |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:01 p.m.