Triple
T495126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GRE |
E10274
|
entity |
| Predicate | hasScoreValidityPeriod |
P8729
|
FINISHED |
| Object | limited number of years after test date |
—
|
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: limited number of years after test date | Statement: [GRE, hasScoreValidityPeriod, limited number of years after test date]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScoreValidityPeriod Context triple: [GRE, hasScoreValidityPeriod, limited number of years after test date]
-
A.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
-
B.
hasOfficialDuration
chosen
Indicates the formally defined length of time associated with an event, process, or entity.
-
C.
hasScoredFor
Indicates that one entity has scored points, goals, or similar achievements on behalf of another entity, such as a team, organization, or side.
-
D.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
E.
dateGranted
Indicates the specific date on which a right, status, or permission was formally conferred or approved.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f0fdd5608190815fa36485df8962 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edf90ca88190b6a182e5b6733612 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.