Triple
T12308029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storkyrkan |
E293402
|
entity |
| Predicate | rebuiltInMaterial |
P59925
|
FINISHED |
| Object | brick |
—
|
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 | Statement: [Storkyrkan, rebuiltInMaterial, brick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebuiltInMaterial Context triple: [Storkyrkan, rebuiltInMaterial, brick]
-
A.
rebuiltFor
Indicates that one entity has been reconstructed, renovated, or modified specifically to serve the needs, purposes, or use of another entity.
-
B.
hasReconstructionMaterial
chosen
Indicates that something is associated with, composed of, or utilizes a particular material for its reconstruction.
-
C.
rebuiltUnder
Indicates that an entity was reconstructed or restored while being subject to the authority, control, or governance of another entity.
-
D.
rebuiltInStone
Indicates that a previously existing structure was reconstructed using stone as the primary building material.
-
E.
rebuiltInterior
Indicates that the interior of an entity has been reconstructed or significantly renovated, typically after damage, aging, or redesign.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.