Triple
T2718695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford English |
E60027
|
entity |
| Predicate | standardWithin |
P41831
|
FINISHED |
| Object | British broadcasting |
—
|
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: British broadcasting | Statement: [Oxford English, standardWithin, British broadcasting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardWithin Context triple: [Oxford English, standardWithin, British broadcasting]
-
A.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
B.
standardBefore
Indicates that one standard must be satisfied, applied, or occur earlier in sequence or priority than another standard.
-
C.
standardApplied
Indicates that a particular standard, rule, or guideline has been put into effect or used as the basis for an action or decision in the relationship.
-
D.
standardBody
Indicates that an entity conforms to a recognized or officially accepted body type, form, or physical specification.
-
E.
standardState
Indicates that an entity is in its default, reference, or officially recognized condition or configuration under standard conditions.
- F. None of above. chosen
Provenance (4 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaaee104819085966bc54d5da9c0 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8240920819087a812d816a55edb |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd949c120819099a9d56eb71a0339 |
completed | March 7, 2026, 7:52 a.m. |
Created at: March 6, 2026, 9:55 p.m.