Triple
T21926491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De triangulis omnimodis |
E541455
|
entity |
| Predicate | printingStatus |
P146589
|
FINISHED |
| Object | circulated in manuscript before print |
—
|
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: circulated in manuscript before print | Statement: [De triangulis omnimodis, printingStatus, circulated in manuscript before print]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: printingStatus Context triple: [De triangulis omnimodis, printingStatus, circulated in manuscript before print]
-
A.
printingCompleted
Indicates that a printing process or job has finished successfully and is no longer in progress.
-
B.
printingSupport
Indicates that one entity provides or is compatible with printing capabilities or services for another entity.
-
C.
printingCenter
Indicates a relationship where one entity serves as the printing center (i.e., the facility or service that performs printing) for another entity.
-
D.
printingColor
Indicates that one entity uses or displays a specific color in the context of printing or printed output.
-
E.
printingLanguage
Indicates the language in which a text, document, or inscription is printed.
- 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123fb6af08190b3562f547d4d2895 |
completed | April 28, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
| PDg | Predicate description generation | batch_69e6fb6991948190a428c3c3bfd1c3b8 |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 7:46 p.m.