Triple
T31521546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J-o-n-t-y |
E804218
|
entity |
| Predicate | hasHyphenationPattern |
P64072
|
FINISHED |
| Object | J-o-n-t-y |
—
|
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: J-o-n-t-y | Statement: [J-o-n-t-y, hasHyphenationPattern, J-o-n-t-y]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHyphenationPattern Context triple: [J-o-n-t-y, hasHyphenationPattern, J-o-n-t-y]
-
A.
hasHyphenation
chosen
Indicates that one entity specifies or provides the hyphenated form or hyphenation pattern of another entity.
-
B.
hasPunctuationSystem
Indicates that an entity possesses or employs a system of punctuation marks for structuring written language.
-
C.
hasPartOfSpeechPattern
Indicates that something (such as a phrase, sentence, or expression) follows or exhibits a specific pattern of parts of speech.
-
D.
hasStressPattern
Indicates that an entity (such as a word or phrase) follows a particular arrangement of stressed and unstressed units (e.g., syllables) in its pronunciation.
-
E.
hasSpellingWithAccent
Indicates that one form of a word or name is spelled using accented characters compared to another form.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:56 p.m.