Triple
T36666233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1983 NFL season |
E905272
|
entity |
| Predicate | draftDateStart |
P288
|
FINISHED |
| Object | 1983-04-26 |
—
|
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: 1983-04-26 | Statement: [1983 NFL season, draftDateStart, 1983-04-26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: draftDateStart Context triple: [1983 NFL season, draftDateStart, 1983-04-26]
-
A.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
B.
startDateConstraint
Indicates a restriction or condition placed on when something is allowed to start, typically specifying valid or required start dates.
-
C.
createdBetween
Indicates that something was created within a specified start and end time or date range.
-
D.
effectivePeriodStart
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
E.
startDateAsGuerrilla
Indicates the date on which an entity began operating or acting in a guerrilla capacity.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c780ecd0819080da2a286bf91257 |
completed | May 3, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.