Triple
T4548060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novum Instrumentum omne |
E110092
|
entity |
| Predicate | numberOfEditionsByErasmus |
P6584
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Novum Instrumentum omne, numberOfEditionsByErasmus, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfEditionsByErasmus Context triple: [Novum Instrumentum omne, numberOfEditionsByErasmus, 5]
-
A.
numberOfEditions
chosen
Indicates the total count of distinct editions associated with a given entity.
-
B.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
-
C.
hasScholarlyEdition
Indicates that an entity has an associated scholarly (critically edited and annotated) edition prepared according to academic standards.
-
D.
hasDifferentEditions
Indicates that an entity exists in multiple distinct versions or editions that differ in some characteristics.
-
E.
eraOfMajorWorks
Indicates the historical period during which an entity produced its most significant or influential works.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57f272248190983ae439bd0ac0cc |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.