Triple
T4738648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gayatri |
E105184
|
entity |
| Predicate | hasSyllabicPattern |
P18519
|
FINISHED |
| Object | 8-8-8 |
—
|
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: 8-8-8 | Statement: [Gayatri, hasSyllabicPattern, 8-8-8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSyllabicPattern Context triple: [Gayatri, hasSyllabicPattern, 8-8-8]
-
A.
hasSyllabicStructure
chosen
Indicates that an entity possesses a specific arrangement or pattern of syllables, such as their number, order, or type.
-
B.
hasSyllableStructure
Indicates that an entity (typically a word or morpheme) possesses a particular arrangement or pattern of syllables.
-
C.
hasSyllableCount
Indicates that one entity (typically a word or phrase) possesses a specific number of syllables given by the other entity.
-
D.
hasSyllabary
Indicates that one entity possesses or is associated with a specific syllabary writing system used to represent its language or notation.
-
E.
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.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6485d690819098dc4a974516da6b |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.