Triple
T14783417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Martin Chapel near Furtwangen |
E347448
|
entity |
| Predicate | architecturalScale |
P87178
|
FINISHED |
| Object | small |
—
|
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: small | Statement: [St. Martin Chapel near Furtwangen, architecturalScale, small]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalScale Context triple: [St. Martin Chapel near Furtwangen, architecturalScale, small]
-
A.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
-
B.
architecturalPlanner
Indicates a relationship where an entity is responsible for designing, organizing, or planning the architectural structure or layout of another entity.
-
C.
buildingScale
chosen
Indicates the relative size or dimensional scale at which a building or architectural structure is designed, represented, or evaluated.
-
D.
architecturalUse
Indicates how a structure, space, or element is intended to be used or function within an architectural context.
-
E.
architecturalWork
Indicates that one entity is an architectural creation (such as a building or structure) designed or realized by 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deca9f1c9c8190a8b28ba0ddd3e2e3 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.