Triple
T34423652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfonsine Tables |
E883613
|
entity |
| Predicate | notablePrintedEditionPlace |
P139306
|
FINISHED |
| Object | Venice |
E21687
|
NE 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: Venice | Statement: [Alfonsine Tables, notablePrintedEditionPlace, Venice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePrintedEditionPlace Context triple: [Alfonsine Tables, notablePrintedEditionPlace, Venice]
-
A.
notableEditionLocation
chosen
Indicates the place where a particularly significant or notable edition of a work was produced, published, or is held.
-
B.
hasPublicationPlace
Indicates the place or location where a publication was produced, issued, or made publicly available.
-
C.
laterPlaceOfPublication
Indicates that a work was published again at a subsequent time in a different place than its original place of publication.
-
D.
publisherLocation
Indicates the place or geographic location where a work is published or where its publisher is based.
-
E.
printedInCity
Indicates that something (such as a document, book, or item) was printed in a particular city.
- F. None of above.
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_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a370db50c78819091d9d0219e17c0a3 |
completed | June 20, 2026, 10:01 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2 a.m.