Triple
T2542644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panaetius of Rhodes |
E57818
|
entity |
| Predicate | worksStatus |
P39444
|
FINISHED |
| Object | survives only in fragments and testimonia |
—
|
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: survives only in fragments and testimonia | Statement: [Panaetius of Rhodes, worksStatus, survives only in fragments and testimonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksStatus Context triple: [Panaetius of Rhodes, worksStatus, survives only in fragments and testimonia]
-
A.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
B.
workOn
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
-
C.
worksAs
Indicates that an entity performs the role, job, or occupation specified by another entity.
-
D.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another entity.
-
E.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
- F. None of above. chosen
Provenance (4 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2bd92f88190bf100c799f62210c |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1c7b6e48190be9a0c31069df797 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:47 p.m.