Triple
T26197854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J. |
E655154
|
entity |
| Predicate | uppercaseFormOf |
P20860
|
FINISHED |
| Object | j |
—
|
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: j | Statement: [J., uppercaseFormOf, j]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uppercaseFormOf Context triple: [J., uppercaseFormOf, j]
-
A.
hasUppercaseForm
chosen
Indicates that one textual entity is the uppercase version or representation of another textual entity.
-
B.
preferredCapitalization
Indicates the specific way a term’s letters should be capitalized when it is written or displayed.
-
C.
usesCapitalization
Indicates that one entity applies specific capitalization (such as upper/lower case or title case) to another entity, typically a string or text element.
-
D.
letterCase
Indicates the relationship between a character or string and its typographical case (such as uppercase, lowercase, or mixed case).
-
E.
isUppercasePreferred
Indicates that uppercase letters are favored or expected over other letter cases in a given context.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cd8c4608190bdf0cc6142264239 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:47 p.m.