Triple
T17314935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winipēk |
E420396
|
entity |
| Predicate | orthographyUses |
P85535
|
FINISHED |
| Object | macron over e |
—
|
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: macron over e | Statement: [Winipēk, orthographyUses, macron over e]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orthographyUses Context triple: [Winipēk, orthographyUses, macron over e]
-
A.
usesStandardOrthographyOf
Indicates that one entity writes or represents language according to the standard orthographic system defined for another entity.
-
B.
orthographicIndependence
Indicates that one writing system or orthographic form functions independently of, and is not derived from or constrained by, another.
-
C.
hasOrthographyStatus
Indicates the orthographic status or condition of how something is written or spelled, such as its conformity to a particular writing system or standard.
-
D.
hasOrthographicConvention
Indicates that there is a specific writing or spelling convention that governs how something is represented in written form.
-
E.
spellingStyle
chosen
Indicates the particular orthographic convention or system of spelling that is used or preferred in 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4399c6ad88190ba7fcf1d2d53171c |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.