Triple
T31298259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Love Symbol |
E798139
|
entity |
| Predicate | unpronounceable |
P123533
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Love Symbol, unpronounceable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unpronounceable Context triple: [The Love Symbol, unpronounceable, true]
-
A.
avoidsPronunciationOf
Indicates that one entity deliberately refrains from saying or articulating the name, word, or expression associated with another entity.
-
B.
cannotBeEasilySpokenBy
chosen
Indicates that one entity (typically a word, phrase, or name) is difficult for another entity (typically a speaker or group) to pronounce or articulate smoothly.
-
C.
notFullyPhonetic
Indicates that the representation of a word or utterance does not capture all of its sounds in a strictly phonetic manner.
-
D.
nonVocal
Indicates that the subject does not produce vocal sounds or speech in the context of the described action or state.
-
E.
unstressedSyllable
Indicates that a given syllable in a word or utterance is not emphasized or accented in pronunciation relative to other syllables.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:14 p.m.