Triple
T13942061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miss |
E335280
|
entity |
| Predicate | politenessRegister |
P9808
|
FINISHED |
| Object | polite |
—
|
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: polite | Statement: [Miss, politenessRegister, polite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politenessRegister Context triple: [Miss, politenessRegister, polite]
-
A.
politenessLevel
Indicates the degree of courteousness or respectfulness expressed by one entity toward another in an interaction.
-
B.
hasPolitePronoun
Indicates that one entity refers to another using a polite or honorific form of address in language.
-
C.
hasPolitenessSystem
chosen
Indicates that a language or communication system includes formalized ways of expressing different levels of politeness or social hierarchy.
-
D.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
E.
honorificUsage
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2cf6e29881908ddb8efca9a456a3 |
completed | April 14, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:17 p.m.