Triple
T33049055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priscus of Panium |
E845674
|
entity |
| Predicate | worksSurvival |
P184878
|
FINISHED |
| Object | fragmentary |
—
|
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: fragmentary | Statement: [Priscus of Panium, worksSurvival, fragmentary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksSurvival Context triple: [Priscus of Panium, worksSurvival, fragmentary]
-
A.
helpsSurvive
Indicates that one entity provides support or advantage that increases another entity’s chances of survival.
-
B.
survivingUse
Indicates that one entity continues to make use of another entity or resource after an event that could have ended or invalidated that use.
-
C.
survivalTheme
Indicates that the relationship or situation centers on the struggle to stay alive or endure extreme hardship.
-
D.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
E.
hasSurvivalSkill
Indicates that an entity possesses the ability or knowledge necessary to endure and function effectively in challenging or threatening conditions.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: May 1, 2026, 1:24 a.m.