Triple
T27650678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julienn |
E696843
|
entity |
| Predicate | hasFinalLetters |
P130930
|
FINISHED |
| Object | -enn |
—
|
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: -enn | Statement: [Julienn, hasFinalLetters, -enn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinalLetters Context triple: [Julienn, hasFinalLetters, -enn]
-
A.
hasFinalFormLetters
Indicates that certain letters in a script change to a distinct "final" shape when they appear at the end of a word.
-
B.
usesFinalConsonants
Indicates that an entity employs or contains consonant sounds in final position, such as at the end of a word, syllable, or phonological unit.
-
C.
hasFinalSyllable
Indicates that one entity possesses or ends with a specific final syllable represented by the other entity.
-
D.
usesInitialsAndFinals
Indicates that the entity represents or expresses something by combining initial components with final components (such as initials with finals in a phonetic or naming system).
-
E.
hasLetterSuffix
chosen
Indicates that an entity’s identifier, name, or code ends with a specific letter or sequence of letters.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 27, 2026, 2:31 p.m.