Triple
T9609120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAN-nee |
E232052
|
entity |
| Predicate | indicatesSecondaryStressOn |
P4253
|
FINISHED |
| Object | no syllable |
—
|
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: no syllable | Statement: [FAN-nee, indicatesSecondaryStressOn, no syllable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesSecondaryStressOn Context triple: [FAN-nee, indicatesSecondaryStressOn, no syllable]
-
A.
secondSyllable
Indicates that the second syllable of one linguistic unit corresponds to, matches, or is identified as a particular syllable or sound in relation to another entity.
-
B.
hasStressPattern
chosen
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.
-
C.
secondSyllableTone
Indicates that the relationship specifies the tonal value or pitch pattern of the second syllable in a word or utterance.
-
D.
secondLetter
Indicates that one entity is the second letter (in sequence or position) of another entity, typically a string or word.
-
E.
secondaryTone
Indicates that one tone functions as a secondary or supporting tonal element in relation to a primary tone within a given context.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a8469e081909c8fb7c84ffea2b3 |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.