Triple
T31259927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Athena (Paestum) |
E797088
|
entity |
| Predicate | hasNumberOfColumnsOnLongSide |
P195095
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [Temple of Athena (Paestum), hasNumberOfColumnsOnLongSide, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfColumnsOnLongSide Context triple: [Temple of Athena (Paestum), hasNumberOfColumnsOnLongSide, 13]
-
A.
numberOfColumnsPerShortSide
Indicates the count of columns that appear along each of the shorter sides of a rectangular or similarly shaped structure or layout.
-
B.
hasNumberOfStandingColumns
Indicates the relationship specifying how many standing columns an entity currently has.
-
C.
hasColumnCountBack
Indicates that an entity (such as a table or layout) has a specified number of columns on its back side or rear-facing section.
-
D.
numberOfColumnsOnFlanks
Indicates the count of columns located on the flanking sides of a structure or object.
-
E.
numberOfColumns
Indicates the total count of vertical divisions (columns) associated with or contained in a given structure or dataset.
- 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_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
| PDg | Predicate description generation | batch_69fda4fe67a08190bdaa84ceabd6de6c |
completed | May 8, 2026, 8:55 a.m. |
Created at: April 29, 2026, 9:12 p.m.