Triple
T29090369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arch of Galerius |
E734835
|
entity |
| Predicate | numberOfArchesPreserved |
P9131
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Arch of Galerius, numberOfArchesPreserved, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfArchesPreserved Context triple: [Arch of Galerius, numberOfArchesPreserved, 2]
-
A.
hasNumberOfArches
chosen
Indicates the relationship specifying how many arches are present in or associated with a given entity.
-
B.
hasMultipleTiersOfArches
Indicates that the subject structure features more than one horizontal level or row of arches stacked vertically.
-
C.
widthOfArches
Indicates the measurement of how wide the arches are in a given structure or context.
-
D.
numberInPreservation
Indicates that an entity has a specified quantity or count within a preservation context (such as items preserved, stored, or maintained).
-
E.
hasNumberOfArchitecturalOrders
Indicates the specific count of architectural orders associated with or present in a given structure or architectural element.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69ffc7b4c7f88190b6357a44e7f0940f |
completed | May 9, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69ffc755f09c8190995ca00d97336988 |
completed | May 9, 2026, 11:46 p.m. |
Created at: April 28, 2026, 11:04 a.m.