Triple
T3994869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TOEIC |
E87074
|
entity |
| Predicate | domainFocus |
P53727
|
FINISHED |
| Object | business English |
—
|
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: business English | Statement: [TOEIC, domainFocus, business English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainFocus Context triple: [TOEIC, domainFocus, business English]
-
A.
brandFocus
Indicates that a brand primarily concentrates its efforts, messaging, or resources on a particular target, theme, or market segment.
-
B.
distributionFocus
Indicates that the primary emphasis or priority within a process, strategy, or system is placed on how something is distributed or allocated.
-
C.
trafficFocus
Indicates a focus of attention or priority given to a particular traffic element, flow, or direction within a transportation or network context.
-
D.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
-
E.
publicDomain
Indicates that a work or resource is not protected by intellectual property rights and is freely available for anyone to use, copy, modify, and distribute without restriction.
- 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_69aed94118148190975e6aa4e554cde9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefb7f92348190ae35f1d75b0b5d4f |
completed | March 9, 2026, 4:55 p.m. |
Created at: March 9, 2026, 3:34 p.m.