Triple
T1539608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARG |
E32833
|
entity |
| Predicate | typicalCase |
P2204
|
FINISHED |
| Object | uppercase |
—
|
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: uppercase | Statement: [ARG, typicalCase, uppercase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCase Context triple: [ARG, typicalCase, uppercase]
-
A.
typicalCaseTypes
Indicates the kinds or categories of cases that are most commonly associated with or handled by a given entity.
-
B.
letterCase
chosen
Indicates the relationship between a character or string and its typographical case (such as uppercase, lowercase, or mixed case).
-
C.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
D.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
E.
typicalPractice
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
- 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_69a885ed29088190a3c2d5a3d100c16e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa95c1a2948190a2b98469afec1a7d |
completed | March 6, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69a907b2453c8190a41f6b88c8217d1e |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.