Triple
T18765933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Americanist phonetic notation |
E458893
|
entity |
| Predicate | hasSymbolFor |
P133459
|
FINISHED |
| Object | ejective consonants |
—
|
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: ejective consonants | Statement: [Americanist phonetic notation, hasSymbolFor, ejective consonants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSymbolFor Context triple: [Americanist phonetic notation, hasSymbolFor, ejective consonants]
-
A.
hasSymbolNamedAfter
Indicates that one entity has a symbol whose name is derived from or dedicated to another entity.
-
B.
hasMainSymbol
Indicates that one entity is designated as the primary or most representative symbol associated with another entity.
-
C.
hasSymbolLocation
Indicates that a symbol is associated with or positioned at a specific location.
-
D.
appearsWithSymbol
Indicates that one entity is shown or presented together with a particular symbol in the same visual or contextual setting.
-
E.
isSameSymbolAs
Indicates that two entities represent the identical symbol or sign, regardless of their specific instances or contexts.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d84cfa881909a1d3f7a5ab82574 |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:52 a.m.