Triple
T3994839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TOEIC |
E87074
|
entity |
| Predicate | primaryContext |
P48472
|
FINISHED |
| Object | professional contexts |
—
|
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: professional contexts | Statement: [TOEIC, primaryContext, professional contexts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryContext Context triple: [TOEIC, primaryContext, professional contexts]
-
A.
primaryFunctionContext
Indicates the main situational or operational context in which a function, role, or process is primarily intended to be used or performed.
-
B.
primaryWorkContext
chosen
Indicates the main environment, setting, or domain in which an entity typically performs its work or primary activities.
-
C.
primaryMode
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
-
D.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
E.
primaryService
Indicates that one entity serves as the main or principal service provided or used in relation to another entity.
- 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_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. |
Created at: March 9, 2026, 3:34 p.m.