Triple
T31731213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corinthian order |
E809862
|
entity |
| Predicate | typicalColumnBaseType |
P207506
|
FINISHED |
| Object | Attic base |
E192253
|
NE 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: Attic base | Statement: [Corinthian order, typicalColumnBaseType, Attic base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalColumnBaseType Context triple: [Corinthian order, typicalColumnBaseType, Attic base]
-
A.
columnType
Indicates the specific data type assigned to a column within a table or dataset.
-
B.
baseType
Indicates that one entity serves as the underlying or parent type from which another entity is derived or specialized.
-
C.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
D.
dataDatatype
Indicates that a piece of data is associated with, or constrained to, a specific datatype.
-
E.
typicalConformingType
Indicates that one entity is a standard or representative instance that conforms to the defining characteristics or constraints of another entity’s type.
- F. None of above. chosen
Provenance (5 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b94776b088190bbbcee27f0a33af9 |
completed | June 12, 2026, 5:09 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 11:21 p.m.