Triple
T24415237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Aphrodite at Knidos |
E615565
|
entity |
| Predicate | viewingPractice |
P79540
|
FINISHED |
| Object | statue could be viewed from multiple sides |
—
|
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: statue could be viewed from multiple sides | Statement: [Temple of Aphrodite at Knidos, viewingPractice, statue could be viewed from multiple sides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewingPractice Context triple: [Temple of Aphrodite at Knidos, viewingPractice, statue could be viewed from multiple sides]
-
A.
viewingIs
Indicates that one entity is engaged in the act or state of viewing, observing, or watching another entity.
-
B.
viewingMethod
chosen
Indicates the manner or technique by which something is observed, displayed, or visually accessed.
-
C.
exhibitionPractice
Indicates the practice or method by which something is displayed or presented in an exhibition context.
-
D.
viewIs
Indicates that one entity is a visual representation or perspective of another entity.
-
E.
coversPractice
Indicates that one entity includes, addresses, or provides instruction on a particular practice or set of practices.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29584d7b88190b35843d3c4e81e03 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:12 a.m.