Triple
T33265300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speed |
E851626
|
entity |
| Predicate | workApproximateDate |
P90615
|
FINISHED |
| Object | early 1590s |
—
|
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: early 1590s | Statement: [Speed, workApproximateDate, early 1590s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workApproximateDate Context triple: [Speed, workApproximateDate, early 1590s]
-
A.
associatedWorkDate
chosen
Indicates the date on which a related or associated work (such as a publication, performance, or creation) is linked to the subject entity.
-
B.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
C.
workPremiereApproximate
Indicates that the premiere of a work occurred around, but not necessarily exactly on, a specified date or time.
-
D.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
-
E.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:32 a.m.