Triple
T17657702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gol |
E440167
|
entity |
| Predicate | hasReplicaBuilding |
P128423
|
FINISHED |
| Object | Gol Stave Church replica |
—
|
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: Gol Stave Church replica | Statement: [Gol, hasReplicaBuilding, Gol Stave Church replica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReplicaBuilding Context triple: [Gol, hasReplicaBuilding, Gol Stave Church replica]
-
A.
hasBuildingStatus
Indicates the current condition, classification, or operational state assigned to a building.
-
B.
hasBuildingFrom
Indicates a relationship where a location or site possesses or includes a building that originates from, or was constructed in, a specified time period, source, or context.
-
C.
hasBuildingPeriod
Indicates that a building or structure is associated with a specific time period during which it was constructed or significantly developed.
-
D.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
E.
hasBuildingFunction
Indicates that a building is used for or serves a particular function or purpose.
- F. None of above. chosen
Provenance (4 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea3b4cc81908eec7032cf221d49 |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 9:28 a.m.