Triple
T33569783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman bridge of Salamanca |
E859862
|
entity |
| Predicate | hasOriginalRomanArches |
P115122
|
FINISHED |
| Object | 15 |
—
|
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: 15 | Statement: [Roman bridge of Salamanca, hasOriginalRomanArches, 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalRomanArches Context triple: [Roman bridge of Salamanca, hasOriginalRomanArches, 15]
-
A.
hasNumberOfArchitecturalOrders
Indicates the specific count of architectural orders associated with or present in a given structure or architectural element.
-
B.
hasRomanRemains
chosen
Indicates that the subject contains or is the location of physical remains or archaeological evidence from the Roman period.
-
C.
hasOriginalBuildings
Indicates that an entity possesses or still retains its initial or historically first-constructed buildings.
-
D.
hasRomanMonument
Indicates that one entity possesses, contains, or includes a monument of Roman origin or style.
-
E.
architecturalOrigin
Indicates the place, style, or tradition from which an architectural work or design originates.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: May 1, 2026, 1:40 a.m.