Triple
T18907395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Wade |
E462500
|
entity |
| Predicate | hasCapitalizationRule |
P72382
|
FINISHED |
| Object | both components capitalized in English |
—
|
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: both components capitalized in English | Statement: [John Wade, hasCapitalizationRule, both components capitalized in English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalizationRule Context triple: [John Wade, hasCapitalizationRule, both components capitalized in English]
-
A.
capitalizationRequirement
Indicates that a specified text element must follow a particular capitalization rule or standard.
-
B.
isCapitalizationWeighted
Indicates that something is evaluated or adjusted based on the relative capitalization (size or value of capital) of its components.
-
C.
hasCapitalFunction
Indicates that an entity serves as the primary seat of government or main administrative center for another entity.
-
D.
recognizesCapital
Indicates that one entity acknowledges or identifies another entity as the capital of a given region or country.
-
E.
preferredCapitalization
chosen
Indicates the specific way a term’s letters should be capitalized when it is written or displayed.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c52dcb948190a5b6a783512bf7d6 |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.