Triple
T10629567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hegesippus |
E250415
|
entity |
| Predicate | worksLostExceptFor |
P32274
|
FINISHED |
| Object | fragments quoted by later authors |
—
|
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: fragments quoted by later authors | Statement: [Hegesippus, worksLostExceptFor, fragments quoted by later authors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksLostExceptFor Context triple: [Hegesippus, worksLostExceptFor, fragments quoted by later authors]
-
A.
hasLostWorks
chosen
Indicates that an entity has created works that are no longer extant, missing, or have not survived.
-
B.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
C.
worksDestroyedBy
Indicates that certain works have been ruined, demolished, or rendered unusable as a result of the actions or effects of a specified agent or cause.
-
D.
materialWorked
Indicates that an agent performs work or processing on a specified material.
-
E.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df92f8388190a8bcff96809d8eb4 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9 p.m.