Triple
T9471548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sincerely, Me |
E228401
|
entity |
| Predicate | hasTitleCapitalization |
P72382
|
FINISHED |
| Object | Title case |
—
|
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: Title case | Statement: [Sincerely, Me, hasTitleCapitalization, Title case]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleCapitalization Context triple: [Sincerely, Me, hasTitleCapitalization, Title case]
-
A.
isCapitalised
Indicates that a given string or word is written with its first letter in uppercase (and the rest in lowercase, if applicable).
-
B.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
C.
preferredCapitalization
chosen
Indicates the specific way a term’s letters should be capitalized when it is written or displayed.
-
D.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
E.
hasNameInCaseTitle
Indicates that a legal case’s title explicitly contains the name of the referenced 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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fef6f288190b2d158c829b31de9 |
completed | April 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:54 p.m.