Triple
T7152265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MW |
E166718
|
entity |
| Predicate | isCaseInsensitiveInStandardUse |
P9568
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [MW, isCaseInsensitiveInStandardUse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCaseInsensitiveInStandardUse Context triple: [MW, isCaseInsensitiveInStandardUse, true]
-
A.
isCaseInsensitiveInStandard
chosen
Indicates that the comparison, matching, or evaluation of values is performed without distinguishing between uppercase and lowercase characters according to a defined standard.
-
B.
hasCaseInflection
Indicates that a word or phrase changes form to reflect grammatical case (such as nominative, accusative, etc.) in a given language context.
-
C.
isUppercasePreferred
Indicates that uppercase letters are favored or expected over other letter cases in a given context.
-
D.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
E.
caseSensitivityVariant
Indicates that one string or textual form is a variant of another that differs only in letter casing (e.g., uppercase vs lowercase).
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f52c1081908c4fa424d5e965bc |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.