Triple
T3994872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TOEIC |
E87074
|
entity |
| Predicate | scoreValidity |
P32493
|
FINISHED |
| Object | commonly considered valid for 2 years |
—
|
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: commonly considered valid for 2 years | Statement: [TOEIC, scoreValidity, commonly considered valid for 2 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoreValidity Context triple: [TOEIC, scoreValidity, commonly considered valid for 2 years]
-
A.
scoreScale
Indicates the scale or range on which a score or rating is expressed or measured.
-
B.
scoreUsedFor
Indicates that a particular score or rating is used for a specific purpose, decision, or downstream process.
-
C.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
D.
validityType
Indicates the specific kind or category of validity that characterizes how or under what conditions something is considered valid.
-
E.
hasValidity
chosen
Indicates that something possesses a period or condition during which it is considered legally, logically, or functionally acceptable or in force.
- 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.