Triple
T19515378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsar Cannon |
E488263
|
entity |
| Predicate | carriageDate |
P136199
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Tsar Cannon, carriageDate, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriageDate Context triple: [Tsar Cannon, carriageDate, 19th century]
-
A.
dateOfJourney
Indicates the specific calendar date on which a particular journey or trip takes place.
-
B.
crossingDate
Indicates the date on which the crossing event between the related entities took place.
-
C.
deliveryDate
Indicates the specific date on which a product, service, or item is scheduled or expected to be delivered.
-
D.
carriedSince
Indicates that one entity has been continuously carrying or transporting another entity starting from a specified point in time.
-
E.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6359b90f08190b38359dc9e97e11c |
completed | April 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004d3a708190a1c13c8f644f3926 |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:40 p.m.