Triple
T19309271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zwölf Artikel |
E482921
|
entity |
| Predicate | approximatePrintRuns |
P116400
|
FINISHED |
| Object | tens of thousands of copies |
—
|
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: tens of thousands of copies | Statement: [Zwölf Artikel, approximatePrintRuns, tens of thousands of copies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximatePrintRuns Context triple: [Zwölf Artikel, approximatePrintRuns, tens of thousands of copies]
-
A.
estimatedCopiesPrinted
Indicates the approximate number of copies of an item that have been printed.
-
B.
printRun
Indicates the number or instance of times a particular item or edition has been printed or produced.
-
C.
approximateProductionNumber
Indicates that one entity specifies an estimated or non-exact quantity associated with the production output of another entity.
-
D.
hasApproximateNumberOfRuns
chosen
Indicates that an entity is associated with a number of runs that is approximate rather than exact.
-
E.
runsApproximately
Indicates that an entity performs a running action in a manner that is close to, but not exactly matching, a specified time, distance, speed, or other running-related measure.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e604cc62e08190b5ba5dfc44efdc5c |
completed | April 20, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.