Triple
T21248796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Khnum at Esna |
E523685
|
entity |
| Predicate | hasColumnCapitalTypes |
P138031
|
FINISHED |
| Object | varied floral capitals |
—
|
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: varied floral capitals | Statement: [Temple of Khnum at Esna, hasColumnCapitalTypes, varied floral capitals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColumnCapitalTypes Context triple: [Temple of Khnum at Esna, hasColumnCapitalTypes, varied floral capitals]
-
A.
columnCapitalType
Indicates that a column represents a type or classification of capital (e.g., financial, physical, human) associated with the data it stores.
-
B.
hasCapitalFunction
Indicates that an entity serves as the primary seat of government or main administrative center for another entity.
-
C.
hasColumnSigns
chosen
Indicates that a column or pillar displays one or more signs, symbols, or inscriptions on its surface.
-
D.
hasColumns
Indicates that one entity possesses or is characterized by a set of columns associated with it.
-
E.
hasCapitalType
Indicates that a specified location’s capital is of a particular type (e.g., political, administrative, or economic capital).
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7359c7a648190b4345336ac3be024 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:56 p.m.