Triple
T16905984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theopompus of Chios |
E424562
|
entity |
| Predicate | workExtent |
P86452
|
FINISHED |
| Object | Hellenica originally comprised 12 books |
—
|
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: Hellenica originally comprised 12 books | Statement: [Theopompus of Chios, workExtent, Hellenica originally comprised 12 books]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workExtent Context triple: [Theopompus of Chios, workExtent, Hellenica originally comprised 12 books]
-
A.
workLength
Indicates the duration or length of time associated with a particular work or task.
-
B.
workScope
Indicates the defined range, extent, and boundaries of tasks or responsibilities involved in a particular work activity or project.
-
C.
originalExtent
chosen
Indicates the total size or scope that something initially had before any reduction, alteration, or loss.
-
D.
workScale
Indicates the relative magnitude, intensity, or scope at which a given work activity, project, or operation is carried out.
-
E.
estimatedWorkingsLength
Indicates the expected or calculated duration or extent of the workings involved in a task, project, or operation.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3ca392ff48190ab28f0bd3e9fc376 |
completed | April 18, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.