Triple
T24240854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pomone |
E603217
|
entity |
| Predicate | survivingMaterial |
P66558
|
FINISHED |
| Object | fragments of the score |
—
|
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 the score | Statement: [Pomone, survivingMaterial, fragments of the score]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingMaterial Context triple: [Pomone, survivingMaterial, fragments of the score]
-
A.
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.
-
B.
helpsSurvive
Indicates that one entity provides support or advantage that increases another entity’s chances of survival.
-
C.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
D.
survivingSources
chosen
Indicates that there exist remaining or extant sources (e.g., documents, records, artifacts) that attest to or provide evidence about the subject.
-
E.
survivesExpedition
Indicates that an entity endures and remains alive through the duration of a specified expedition or journey.
- 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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28a9f812c81909dba8fbb54d8985c |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:03 a.m.