Triple
T691712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test of English as a Foreign Language |
E13805
|
entity |
| Predicate | typicalValidityPeriod |
P16413
|
FINISHED |
| Object | 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: 2 years | Statement: [Test of English as a Foreign Language, typicalValidityPeriod, 2 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalValidityPeriod Context triple: [Test of English as a Foreign Language, typicalValidityPeriod, 2 years]
-
A.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
B.
eligibilityPeriod
chosen
Indicates the span of time during which an entity qualifies for or is allowed to receive a particular benefit, service, or status.
-
C.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
D.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
E.
renewalDate
Indicates the date on which an existing agreement, subscription, or arrangement is scheduled to be renewed or extended.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0aebde88190a49d421477713103 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d221d38819083c0adda81f59b07 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.