Triple
T1270543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parmenides |
E15697
|
entity |
| Predicate | survivingWorkForm |
P28056
|
FINISHED |
| Object | fragments |
—
|
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 | Statement: [Parmenides, survivingWorkForm, fragments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingWorkForm Context triple: [Parmenides, survivingWorkForm, fragments]
-
A.
employsForm
Indicates that an entity makes use of or applies a particular form or format in carrying out an action or function.
-
B.
eligibleWork
Indicates that a particular work satisfies the necessary conditions or criteria to qualify for a specified status, benefit, or consideration.
-
C.
eligibleWorks
Indicates that certain works meet the required criteria or conditions to qualify for a specified status, use, or consideration.
-
D.
helpedForm
Indicates that one entity contributed significantly to the creation, establishment, or founding of another entity.
-
E.
workModel
Indicates that one entity serves as, or is based on, a particular model used for work, operation, or functional behavior.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c0691d70819088e57c78ff34af1e |
completed | March 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bfa205ec81909d8170b398345615 |
completed | March 1, 2026, 10:37 p.m. |
Created at: March 1, 2026, 7:50 p.m.