Triple
T29063300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Apollo Epicurius |
E735598
|
entity |
| Predicate | hasInteriorOrder |
P196819
|
FINISHED |
| Object | Ionic |
—
|
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: Ionic | Statement: [Temple of Apollo Epicurius, hasInteriorOrder, Ionic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteriorOrder Context triple: [Temple of Apollo Epicurius, hasInteriorOrder, Ionic]
-
A.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
B.
hasInteriorItem
Indicates that one entity contains another entity as an item located within its interior.
-
C.
hasOrderDivision
Indicates that one entity is organized into or associated with a specific division or subdivision within an ordered or hierarchical structure.
-
D.
hasInteriorPeriod
Indicates that an entity includes or is associated with a specific time interval occurring within its overall duration.
-
E.
orderWithin
Indicates that one entity is positioned or ranked before or after another entity within a defined sequence or ordering.
- F. None of above. chosen
Provenance (4 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
| PDg | Predicate description generation | batch_69fe6b7a823881909dc2037fe25bea24 |
completed | May 8, 2026, 11:02 p.m. |
Created at: April 28, 2026, 10:16 a.m.