Triple
T30705904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eros of Thespiae |
E781750
|
entity |
| Predicate | hasCopyOrVariant |
P16932
|
FINISHED |
| Object | later Roman copies of Praxitelean Eros type |
—
|
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: later Roman copies of Praxitelean Eros type | Statement: [Eros of Thespiae, hasCopyOrVariant, later Roman copies of Praxitelean Eros type]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCopyOrVariant Context triple: [Eros of Thespiae, hasCopyOrVariant, later Roman copies of Praxitelean Eros type]
-
A.
hasCopy
chosen
Indicates that one entity possesses, contains, or maintains a duplicate or instance of another entity.
-
B.
hasCopyOrClone
Indicates that one entity exists as a copy or clone of another, preserving the original’s content or structure.
-
C.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
D.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
-
E.
hasVariantCovers
Indicates that one entity has alternative or different versions of its covers associated with it.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01839b071481909f9cc79a6a09387d |
completed | May 11, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_6a017edbed688190baa61cbae5110c8e |
completed | May 11, 2026, 7:01 a.m. |
Created at: April 29, 2026, 8:35 p.m.