Triple
T34423651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfonsine Tables |
E883613
|
entity |
| Predicate | earliestMajorEditionDate |
P188131
|
FINISHED |
| Object | 1320s |
—
|
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: 1320s | Statement: [Alfonsine Tables, earliestMajorEditionDate, 1320s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestMajorEditionDate Context triple: [Alfonsine Tables, earliestMajorEditionDate, 1320s]
-
A.
earliestVersionDate
Indicates the date on which the earliest known or first version of an entity was created, released, or became valid.
-
B.
firstTypicalEditionYear
Indicates the year in which the first typical or standard edition of a work was published or officially issued.
-
C.
firstEditionStartDate
Indicates the date on which the first edition of something (such as a work, product, or event series) was initially released or began.
-
D.
firstRecordedEditionYear
Indicates the calendar year in which the first recorded edition of a work was published or documented.
-
E.
firstMajorRunYear
Indicates the year in which something (such as an event, production, or operation) first began its major or primary run.
- F. None of above. chosen
Provenance (4 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: May 1, 2026, 2 a.m.