Triple
T278679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KG |
E5304
|
entity |
| Predicate | styleOfAddressContext |
P4035
|
FINISHED |
| Object | formal written contexts |
—
|
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: formal written contexts | Statement: [KG, styleOfAddressContext, formal written contexts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOfAddressContext Context triple: [KG, styleOfAddressContext, formal written contexts]
-
A.
addressType
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
-
B.
styleGranted
Indicates that a particular style, manner, or mode of expression has been conferred or authorized for use by one entity to another.
-
C.
usesAddressingSystem
Indicates that one entity employs or applies a particular addressing system associated with another entity.
-
D.
usedWithStyle
Indicates that something is employed or applied in conjunction with a particular style or stylistic manner.
-
E.
formalityLevel
chosen
Indicates the degree of social or stylistic formality characterizing an interaction, expression, or context between entities.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25dee7830819087f153769a8496b9 |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b765f488190b2cbe4b45cd42821 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.