Triple
T223604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AScX |
E4267
|
entity |
| Predicate | typeOfCapitalization |
P2204
|
FINISHED |
| Object | small capitalization |
—
|
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: small capitalization | Statement: [AScX, typeOfCapitalization, small capitalization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCapitalization Context triple: [AScX, typeOfCapitalization, small capitalization]
-
A.
letterCase
chosen
Indicates the relationship between a character or string and its typographical case (such as uppercase, lowercase, or mixed case).
-
B.
isCapitalizationWeighted
Indicates that something is evaluated or adjusted based on the relative capitalization (size or value of capital) of its components.
-
C.
hasUppercaseAndLowercase
Indicates that a string or text value contains at least one uppercase letter and at least one lowercase letter.
-
D.
hasCapital
Indicates that a place or political entity has a specific city designated as its capital.
-
E.
usesAlphabet
Indicates that one entity employs or is written using the alphabet or writing system associated with another entity.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dec53ac8190912f3d79576131fa |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b5739dc8190bad8bfa330ce0499 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.