Triple
T10333241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commendatore (Italian) |
E242929
|
entity |
| Predicate | usedHonorificallyAs |
P81246
|
FINISHED |
| Object | form of address |
—
|
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: form of address | Statement: [Commendatore (Italian), usedHonorificallyAs, form of address]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedHonorificallyAs Context triple: [Commendatore (Italian), usedHonorificallyAs, form of address]
-
A.
honorificUsage
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
-
B.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
C.
alternativeHonorificFor
Indicates that one honorific title can be used as an alternative form of address for another honorific.
-
D.
honorificNickname
Indicates that one entity is referred to by a respectful or honorific nickname by another entity or in a given context.
-
E.
usedAsCourtesyTitleFor
chosen
Indicates that one entity serves as a courtesy title or honorific form of address applied 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:53 a.m.