Triple
T17062941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lysippus |
E414007
|
entity |
| Predicate | survivingEvidence |
P66558
|
FINISHED |
| Object | Roman marble copies of his bronzes |
—
|
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: Roman marble copies of his bronzes | Statement: [Lysippus, survivingEvidence, Roman marble copies of his bronzes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingEvidence Context triple: [Lysippus, survivingEvidence, Roman marble copies of his bronzes]
-
A.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
B.
survivingSources
chosen
Indicates that there exist remaining or extant sources (e.g., documents, records, artifacts) that attest to or provide evidence about the subject.
-
C.
survivesIn
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
-
D.
survivesBy
Indicates that one entity continues to live or exist after another entity has died or ceased to exist.
-
E.
survivesWith
Indicates that one entity continues to live, endure, or remain viable in the presence, context, or company of another entity.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3db7eb0808190ae1b0044e2b5cbd7 |
completed | April 18, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.