Triple
T11558837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryc |
E274082
|
entity |
| Predicate | usageCharacteristic |
P2529
|
FINISHED |
| Object | nonstandard spelling |
—
|
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: nonstandard spelling | Statement: [Bryc, usageCharacteristic, nonstandard spelling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usageCharacteristic Context triple: [Bryc, usageCharacteristic, nonstandard spelling]
-
A.
usageType
chosen
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
B.
usageAmong
Indicates how frequently or in what manner something is used within a particular group, context, or population.
-
C.
managementCharacteristic
Indicates a defining quality, style, or attribute associated with how something is managed or administered.
-
D.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
-
E.
domainCharacteristic
Indicates that a domain or area of interest possesses a particular characteristic or defining property.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a888e8481909386009b9603e4d3 |
completed | April 10, 2026, 5:28 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.