Triple
T29989433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo Sauroktonos |
E761829
|
entity |
| Predicate | hasRomanCopies |
P170146
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Apollo Sauroktonos, hasRomanCopies, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanCopies Context triple: [Apollo Sauroktonos, hasRomanCopies, yes]
-
A.
isRomanCopyOf
chosen
Indicates that one entity is a Roman-era reproduction or version of another, typically earlier, work.
-
B.
hasRomanRemains
Indicates that the subject contains or is the location of physical remains or archaeological evidence from the Roman period.
-
C.
copiedManuscriptsOf
Indicates that one entity has produced or created handwritten reproductions of the manuscripts belonging to another entity.
-
D.
hasRomanMonument
Indicates that one entity possesses, contains, or includes a monument of Roman origin or style.
-
E.
postRomanReuse
Indicates that something originally from the Roman period is used, repurposed, or incorporated again in a later, post-Roman context.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 29, 2026, 6:37 p.m.