Triple
T10645490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Augustus columns |
E250822
|
entity |
| Predicate | hiddenWithin |
P68420
|
FINISHED |
| Object | interior courtyard |
—
|
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: interior courtyard | Statement: [Temple of Augustus columns, hiddenWithin, interior courtyard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hiddenWithin Context triple: [Temple of Augustus columns, hiddenWithin, interior courtyard]
-
A.
hiddenIn
chosen
Indicates that one entity is concealed within, behind, or inside another entity so that it is not readily visible or apparent.
-
B.
hiddenAt
Indicates that one entity is concealed or stored at a specific location or within another entity.
-
C.
hidingPlace
Indicates a location or object that serves as a concealed or secret place where something or someone is hidden.
-
D.
covered
Indicates that one entity lies over or on top of another entity so as to conceal, protect, or obscure it.
-
E.
concealmentType
Indicates the specific manner or method by which something is hidden, obscured, or kept from detection.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfe120908190ab91c38d57133739 |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:05 p.m.