Triple
T21796918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surfin' |
E538116
|
entity |
| Predicate | notableLyricMotto |
P111085
|
FINISHED |
| Object | "You can't stop my shine" |
—
|
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: "You can't stop my shine" | Statement: [Surfin', notableLyricMotto, "You can't stop my shine"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLyricMotto Context triple: [Surfin', notableLyricMotto, "You can't stop my shine"]
-
A.
isMottoOf
Indicates that a phrase or expression serves as the official motto associated with a particular entity.
-
B.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
C.
mottoInscription
Indicates that a particular motto is inscribed on or associated as an inscription with an entity.
-
D.
textualMottoContext
Indicates that a textual motto appears within, or is associated with, a particular contextual source (such as a document, object, or setting) that provides its usage or interpretive background.
-
E.
mottoOrNickname
chosen
Indicates that one entity serves as a motto, slogan, or nickname associated with another entity.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0622502188190998638317f232334 |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.