Triple
T16561590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Classicissima |
E402350
|
entity |
| Predicate | hasEditionCountApprox |
P6584
|
FINISHED |
| Object | over 110 editions |
—
|
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: over 110 editions | Statement: [La Classicissima, hasEditionCountApprox, over 110 editions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEditionCountApprox Context triple: [La Classicissima, hasEditionCountApprox, over 110 editions]
-
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.
hasDifferentEditions
Indicates that an entity exists in multiple distinct versions or editions that differ in some characteristics.
-
D.
majorEditionsPlanned
Indicates that significant future versions or releases of an entity (such as a work, product, or publication) are scheduled or intended to be produced.
-
E.
hasEditionType
Indicates that one entity is a specific edition type or format classification of another entity (such as a work, publication, or product).
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3576eb63081908cb5dc6c0a8a13ac |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.