Triple
T9736179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GIA-co-mo |
E236067
|
entity |
| Predicate | unstressedSyllable |
P90732
|
FINISHED |
| Object | co |
—
|
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: co | Statement: [GIA-co-mo, unstressedSyllable, co]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unstressedSyllable Context triple: [GIA-co-mo, unstressedSyllable, co]
-
A.
firstSyllable
Indicates that one entity is the first syllable occurring at the beginning of another entity (typically a word or phrase).
-
B.
usesSyllables
Indicates that one entity forms, expresses, or analyzes something by employing syllables as its basic units.
-
C.
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.
-
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.
notFullyPhonetic
Indicates that the representation of a word or utterance does not capture all of its sounds in a strictly phonetic manner.
- F. None of above. chosen
Provenance (4 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9eee70d48190af5a833d7b33aaa5 |
completed | April 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd07c5c978819084abc7267a5ced80 |
completed | April 1, 2026, 11:55 a.m. |
Created at: March 30, 2026, 8:22 p.m.