Triple
T25100816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Didymus Chalcenterus |
E628715
|
entity |
| Predicate | estimatedNumberOfWorks |
P146519
|
FINISHED |
| Object | over 3,500 books according to ancient sources |
—
|
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 3,500 books according to ancient sources | Statement: [Didymus Chalcenterus, estimatedNumberOfWorks, over 3,500 books according to ancient sources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedNumberOfWorks Context triple: [Didymus Chalcenterus, estimatedNumberOfWorks, over 3,500 books according to ancient sources]
-
A.
approximateNumberOfWorks
chosen
Indicates an estimated or roughly calculated count of works associated with an entity.
-
B.
numberOfWorks
Indicates the total count of works associated with a given entity.
-
C.
numberOfWorksCreated
Indicates the total count of creative works that an entity has produced or authored.
-
D.
estimatedWorkingsLength
Indicates the expected or calculated duration or extent of the workings involved in a task, project, or operation.
-
E.
numberOfManuscriptsApprox
Indicates an approximate count of manuscripts associated with an entity.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464bd4d7081909fc0db6b8bf897b9 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:25 a.m.