Triple
T35319121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeus Lepsynos |
E1019987
|
entity |
| Predicate | hasTempleOrder |
P143119
|
FINISHED |
| Object | Ionic order |
—
|
NE NERFINISHED |
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: Ionic order | Statement: [Zeus Lepsynos, hasTempleOrder, Ionic order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTempleOrder Context triple: [Zeus Lepsynos, hasTempleOrder, Ionic order]
-
A.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
B.
hasTempleTree
Indicates that a location or entity possesses or contains a temple-associated tree.
-
C.
hasTempleCount
Indicates that an entity is associated with a specified number of temples.
-
D.
hasTempleLocation
Indicates that a temple is located at or associated with a specific place or geographic location.
-
E.
hasTempleFeature
chosen
Indicates that an entity possesses a specific architectural or structural feature characteristic of a 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 3, 2026, 4:03 p.m.