Triple
T16980404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadrian’s Arch (Jerash) |
E411927
|
entity |
| Predicate | hasSideArchways |
P81958
|
FINISHED |
| Object | two smaller lateral openings |
—
|
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: two smaller lateral openings | Statement: [Hadrian’s Arch (Jerash), hasSideArchways, two smaller lateral openings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSideArchways Context triple: [Hadrian’s Arch (Jerash), hasSideArchways, two smaller lateral openings]
-
A.
hasSideArch
chosen
Indicates that one entity possesses or features a secondary or lateral arch structure in relation to another entity.
-
B.
hasArchedEntrances
Indicates that an entity features one or more entrances constructed with an arched shape.
-
C.
sideArchType
Indicates the architectural style or structural type used for the side arches in a construction or design.
-
D.
widthOfArches
Indicates the measurement of how wide the arches are in a given structure or context.
-
E.
hasSideWalls
Indicates that an object or structure possesses side walls as part of its physical configuration.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d18776c081909225620fd43aca57 |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.