Triple
T19073314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin letter J |
E466844
|
entity |
| Predicate | typicalCategoryInEnglish |
P12230
|
FINISHED |
| Object | voiced postalveolar affricate |
—
|
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: voiced postalveolar affricate | Statement: [Latin letter J, typicalCategoryInEnglish, voiced postalveolar affricate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCategoryInEnglish Context triple: [Latin letter J, typicalCategoryInEnglish, voiced postalveolar affricate]
-
A.
commonUseCategory
Indicates that multiple entities share the same general category of use or functional purpose.
-
B.
typicalIn
chosen
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
cornerCategory
Indicates that something is classified as belonging to a specific type or category of corner.
-
D.
categoryLabel_N
Indicates that an entity is assigned a specific categorical label or classification name.
-
E.
coreCategory
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e1ce5881908367424c89d73feb |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.