Triple
T21783280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOAD |
E537769
|
entity |
| Predicate | hasUsageStandard |
P1587
|
FINISHED |
| Object | standard American English usage |
—
|
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: standard American English usage | Statement: [NOAD, hasUsageStandard, standard American English usage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUsageStandard Context triple: [NOAD, hasUsageStandard, standard American English usage]
-
A.
usesStandard
chosen
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
B.
usedAsStandard
Indicates that one entity serves as the reference or benchmark against which another entity is measured, compared, or evaluated.
-
C.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
D.
isStandardOn
Indicates that a particular feature, option, or component is included by default as part of another item, rather than being optional or extra.
-
E.
usesStandardType
Indicates that one entity employs or relies on a predefined, commonly accepted standard type defined elsewhere.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0462ed0ec81908833e18c164e8b5c |
completed | April 28, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.