Triple
T9963986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Elizabethan |
E195634
|
entity |
| Predicate | namedServiceStartYear |
P77922
|
FINISHED |
| Object | 1953 |
—
|
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: 1953 | Statement: [The Elizabethan, namedServiceStartYear, 1953]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedServiceStartYear Context triple: [The Elizabethan, namedServiceStartYear, 1953]
-
A.
designationYear
Indicates the year in which something was formally designated, assigned, or given an official status.
-
B.
coachStartYear
Indicates the year in which a person began serving in a coaching role for a particular team or organization.
-
C.
beganInYear
Indicates that an event, process, or state started in a specific calendar year.
-
D.
startServiceYear
chosen
Indicates the year in which an entity began providing a particular service or started its service-related activity.
-
E.
recordStartYear
Indicates the calendar year in which a particular record, entry, or data instance first began or was created.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb71a33b48190a18c1a9023f249d2 |
completed | April 2, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.