Triple
T31764937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morsum |
E810779
|
entity |
| Predicate | hasLocalArchitecture |
P185635
|
FINISHED |
| Object | brick houses with thatched roofs |
—
|
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: brick houses with thatched roofs | Statement: [Morsum, hasLocalArchitecture, brick houses with thatched roofs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalArchitecture Context triple: [Morsum, hasLocalArchitecture, brick houses with thatched roofs]
-
A.
hasLocalArchitectureStyle
chosen
Indicates that an entity exhibits, follows, or is characterized by an architectural style specific to a particular locality or region.
-
B.
hasArchitectureBy
Indicates that an entity’s architectural design was created or authored by a specified architect or architectural firm.
-
C.
hasSubArchitecture
Indicates that one architectural component or structure is a subordinate or constituent part of a larger overarching architecture.
-
D.
usesArchitecture
Indicates that one entity is built, implemented, or operates according to the architectural style, framework, or design specified by another entity.
-
E.
hasArchitecturalSupport
Indicates that one entity provides structural or design backing, compatibility, or enablement for another within an architectural context.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: April 30, 2026, 11:32 p.m.