Triple
T18243418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Big Sombrero |
E436878
|
entity |
| Predicate | shapeInspiredNickname |
P130994
|
FINISHED |
| Object | sombrero-like upper deck |
—
|
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: sombrero-like upper deck | Statement: [The Big Sombrero, shapeInspiredNickname, sombrero-like upper deck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shapeInspiredNickname Context triple: [The Big Sombrero, shapeInspiredNickname, sombrero-like upper deck]
-
A.
nameTheme
Indicates that one entity serves as the thematic or subject-related name associated with another entity.
-
B.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
-
C.
nicknameCoinedIn
Indicates that a particular nickname was first created, introduced, or came into use in a specified time or context.
-
D.
nickNameMeaning
Indicates that a nickname is associated with a particular meaning, interpretation, or significance.
-
E.
nickNameGivenBy
Indicates that one entity assigns or uses a particular nickname for another entity.
- F. None of above. chosen
Provenance (4 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e4f0548190bc617e6acd17010d |
completed | April 19, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:33 a.m.