Triple
T19242261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gallus |
E481160
|
entity |
| Predicate | survivingTexts |
P131176
|
FINISHED |
| Object | fragments of elegies |
—
|
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 of elegies | Statement: [Gallus, survivingTexts, fragments of elegies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingTexts Context triple: [Gallus, survivingTexts, fragments of elegies]
-
A.
survivingSources
Indicates that there exist remaining or extant sources (e.g., documents, records, artifacts) that attest to or provide evidence about the subject.
-
B.
booksSurvivingPartially
chosen
Indicates that the books in question have only partially survived, with some portions lost or missing.
-
C.
booksSurvivingCompletely
Indicates that the books in question have remained fully intact and unchanged, with no parts lost or damaged.
-
D.
survivalStoryChronicledIn
Indicates that an account of surviving a dangerous or life-threatening situation is documented or recorded within a particular medium or work.
-
E.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faf2353c819094a9a1af3a858715 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:27 p.m.