Triple
T15584190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horace and Pete |
E374575
|
entity |
| Predicate | formalStyle |
P4035
|
FINISHED |
| Object | stage-play style |
—
|
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: stage-play style | Statement: [Horace and Pete, formalStyle, stage-play style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalStyle Context triple: [Horace and Pete, formalStyle, stage-play style]
-
A.
formalSetting
Indicates that the associated interaction, event, or context occurs in a formal or official setting governed by explicit social or institutional norms.
-
B.
formalismFor
Indicates that one entity serves as a formal representation, framework, or notation specifically designed to model, describe, or reason about another entity.
-
C.
formalityLevel
chosen
Indicates the degree of social or stylistic formality characterizing an interaction, expression, or context between entities.
-
D.
officeStyle
Indicates a stylistic or design relationship where one entity’s style is characterized as “office” or suitable for an office environment.
-
E.
formalFunction
Indicates that an entity serves an official or designated role or purpose within a formal structure, system, or context.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e47971481909e986dd999354628 |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:11 a.m.