Triple
T33264634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW |
E851610
|
entity |
| Predicate | chronologicalCriterion |
P194668
|
FINISHED |
| Object | date of printing before 1501 |
—
|
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: date of printing before 1501 | Statement: [GW, chronologicalCriterion, date of printing before 1501]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalCriterion Context triple: [GW, chronologicalCriterion, date of printing before 1501]
-
A.
chronologicalStatus
Indicates the temporal state or phase of something relative to a timeline or sequence of events.
-
B.
chronologyType
Indicates the type or system of chronological ordering or dating applied to an event, period, or sequence.
-
C.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
D.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
E.
chronologicalFunction
Indicates a temporal relationship where one event or state functions to order, structure, or position another within a sequence of time.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
| PDg | Predicate description generation | batch_69fd7fd9be2881908a7f00e0e8822de8 |
completed | May 8, 2026, 6:16 a.m. |
Created at: May 1, 2026, 1:32 a.m.