Triple
T36298482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BrodHead |
E893435
|
entity |
| Predicate | isVariantCapitalizationOf |
P12011
|
FINISHED |
| Object | Brodhead |
—
|
NE NERFINISHED |
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: Brodhead | Statement: [BrodHead, isVariantCapitalizationOf, Brodhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVariantCapitalizationOf Context triple: [BrodHead, isVariantCapitalizationOf, Brodhead]
-
A.
caseSensitivityVariant
chosen
Indicates that one string or textual form is a variant of another that differs only in letter casing (e.g., uppercase vs lowercase).
-
B.
isCapitalizationWeighted
Indicates that something is evaluated or adjusted based on the relative capitalization (size or value of capital) of its components.
-
C.
hasVariantSpelling
Indicates that one term is an alternative spelling form of another term.
-
D.
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.
-
E.
isCapitalised
Indicates that a given string or word is written with its first letter in uppercase (and the rest in lowercase, if applicable).
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.