Triple
T25210393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxfords |
E631668
|
entity |
| Predicate | hasTypicalFormalityLevel |
P4035
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Oxfords, hasTypicalFormalityLevel, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalFormalityLevel Context triple: [Oxfords, hasTypicalFormalityLevel, high]
-
A.
formalityLevel
chosen
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.
formalismType
Indicates the specific formal system or representational framework in which something (such as a theory, model, or specification) is expressed.
-
D.
hasFormalStatus
Indicates that an entity possesses an officially recognized or legally defined status within a formal system or context.
-
E.
politenessLevel
Indicates the degree of courteousness or respectfulness expressed by one entity toward another in an interaction.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 21, 2026, 12:58 p.m.