Triple
T30143313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pont del Diable (Martorell) |
E766183
|
entity |
| Predicate | hasMainArchStyle |
P607
|
FINISHED |
| Object | Gothic arch |
—
|
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: Gothic arch | Statement: [Pont del Diable (Martorell), hasMainArchStyle, Gothic arch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainArchStyle Context triple: [Pont del Diable (Martorell), hasMainArchStyle, Gothic arch]
-
A.
hasMainArch
Indicates that an entity possesses or features a primary or central arch structure.
-
B.
architecturalStyleIncludes
Indicates that a structure, building, or design incorporates or exemplifies a particular architectural style as one of its defining characteristics.
-
C.
architecturalStyle
chosen
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
-
D.
hasLocalArchitectureStyle
Indicates that an entity exhibits, follows, or is characterized by an architectural style specific to a particular locality or region.
-
E.
hasArchType
Indicates that one entity possesses or is characterized by a particular architectural type or style.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
Created at: April 29, 2026, 7:18 p.m.