Triple
T11103882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arch of Augustus (Rimini) |
E262577
|
entity |
| Predicate | hasSingleArchway |
P9131
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Arch of Augustus (Rimini), hasSingleArchway, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSingleArchway Context triple: [Arch of Augustus (Rimini), hasSingleArchway, true]
-
A.
hasSingleHall
Indicates that an entity possesses exactly one hall within its structure or domain.
-
B.
hasSeparateEntrances
Indicates that the related entities each have their own distinct entrance, rather than sharing a common one.
-
C.
hasNumberOfArches
chosen
Indicates the relationship specifying how many arches are present in or associated with a given entity.
-
D.
hasSideArch
Indicates that one entity possesses or features a secondary or lateral arch structure in relation to another entity.
-
E.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a2d33948190ac29d174694a78e5 |
completed | April 9, 2026, 12:23 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.