Triple
T7462416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-List Preferred |
E176282
|
entity |
| Predicate | statusYearStructure |
P72563
|
FINISHED |
| Object | calendar-year based qualification and validity |
—
|
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: calendar-year based qualification and validity | Statement: [A-List Preferred, statusYearStructure, calendar-year based qualification and validity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusYearStructure Context triple: [A-List Preferred, statusYearStructure, calendar-year based qualification and validity]
-
A.
DOCStatusYear
chosen
Indicates the year associated with the status of a document (e.g., when a particular status was assigned or recorded).
-
B.
authorizationYear
Indicates the year in which an official approval, permission, or authorization for something was granted.
-
C.
seasonYears
Indicates the span of calendar years during which a particular season (e.g., of a show, competition, or activity) takes place or is valid.
-
D.
ordinationYear
Indicates the year in which an individual was formally ordained to a religious office or role.
-
E.
standardizedInYear
Indicates the specific year in which something was formally standardized or adopted as a standard.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d80ae08190ba383066cf0cb2ce |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:39 p.m.