Triple
T17322970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conte |
E420605
|
entity |
| Predicate | titleStyleInItalian |
P81918
|
FINISHED |
| Object | Conte di + toponym or family name |
—
|
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: Conte di + toponym or family name | Statement: [Conte, titleStyleInItalian, Conte di + toponym or family name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleStyleInItalian Context triple: [Conte, titleStyleInItalian, Conte di + toponym or family name]
-
A.
titleInItalian
Indicates that one entity is the title of another entity expressed in the Italian language.
-
B.
titleStyleInFull
Indicates that the specified title is presented in its complete, unabridged form, including all stylistic elements or formatting.
-
C.
equivalentTitleInItalian
Indicates that one entity’s title is an equivalent version of another entity’s title expressed in Italian.
-
D.
titleStylization
chosen
Indicates how the written form of a title is stylistically presented, such as through capitalization, spacing, punctuation, or special formatting.
-
E.
titleHolderStyle
Indicates the manner or format in which a title holder’s status or designation is presented or styled in relation to 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d0cf2481908a018593ef39fd18 |
completed | April 19, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.