Triple
T25637737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vdm |
E642751
|
entity |
| Predicate | hasCaseInsensitiveForm |
P20861
|
FINISHED |
| Object | vdm |
—
|
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: vdm | Statement: [Vdm, hasCaseInsensitiveForm, vdm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaseInsensitiveForm Context triple: [Vdm, hasCaseInsensitiveForm, vdm]
-
A.
hasLowercaseForm
chosen
Indicates that one entity is the lowercase version or representation of another entity.
-
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.
isCaseInsensitiveInStandard
Indicates that the comparison, matching, or evaluation of values is performed without distinguishing between uppercase and lowercase characters according to a defined standard.
-
D.
hasUppercaseForm
Indicates that one textual entity is the uppercase version or representation of another textual entity.
-
E.
isCaseSensitiveInStandard
Indicates that the interpretation or comparison of the entity follows a standard in which letter case differences are treated as significant.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 21, 2026, 5:36 p.m.