Triple
T31259928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Athena (Paestum) |
E797088
|
entity |
| Predicate | hasPeripteralPlan |
P192377
|
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: [Temple of Athena (Paestum), hasPeripteralPlan, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeripteralPlan Context triple: [Temple of Athena (Paestum), hasPeripteralPlan, yes]
-
A.
hasCentralPlan
Indicates that an entity is designed or organized according to a central, unified plan or layout.
-
B.
hasPlanningPeriod
Indicates that an entity is associated with a defined time span allocated for planning activities.
-
C.
hasTypicalPlan
Indicates that there is a standard or commonly followed plan, procedure, or course of action typically associated with the given entity or situation.
-
D.
hasCityPlanShape
Indicates that an entity’s overall city layout or urban plan conforms to a particular geometric or structural shape.
-
E.
hasStreetPlan
Indicates that an entity possesses or is associated with a specific layout or design plan for its streets.
- 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_69f224dd5fdc81908a4cd24917b67668 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69fd098357348190a835c0b6d99857d2 |
completed | May 7, 2026, 9:52 p.m. |
Created at: April 29, 2026, 9:12 p.m.