Triple
T23450213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuary of Hera at Samos |
E567757
|
entity |
| Predicate | notableTempleType |
P18959
|
FINISHED |
| Object | dipteral peripteral temple |
—
|
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: dipteral peripteral temple | Statement: [Sanctuary of Hera at Samos, notableTempleType, dipteral peripteral temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTempleType Context triple: [Sanctuary of Hera at Samos, notableTempleType, dipteral peripteral temple]
-
A.
templeType
chosen
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
B.
majorTempleLocation
Indicates that a major temple associated with an entity is located at a specified place.
-
C.
shrineType
Indicates the specific category or kind of shrine associated with an entity.
-
D.
hasNotableTemple
Indicates that an entity is associated with a temple that is recognized as particularly important, famous, or significant.
-
E.
religiousSiteType
Indicates the specific kind or category of religious site associated with an entity (e.g., church, mosque, temple).
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a64c1ee081908ba3adf5ce80d6a5 |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:52 p.m.