Triple
T28171684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Hill |
E715474
|
entity |
| Predicate | indicatesFormality |
P112220
|
FINISHED |
| Object | formal |
—
|
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 | Statement: [Mr. Hill, indicatesFormality, formal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesFormality Context triple: [Mr. Hill, indicatesFormality, formal]
-
A.
formalityLevel
Indicates the degree of social or stylistic formality characterizing an interaction, expression, or context between entities.
-
B.
isLessFormalThan
Indicates that one entity has a lower level of formality or is more casual in style, tone, or usage compared to another entity.
-
C.
titleFormality
chosen
Indicates the degree of formality conveyed by a title used to address or refer to an entity.
-
D.
formalismFor
Indicates that one entity serves as a formal representation, framework, or notation specifically designed to model, describe, or reason about another entity.
-
E.
formalSetting
Indicates that the associated interaction, event, or context occurs in a formal or official setting governed by explicit social or institutional norms.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 10:13 p.m.