Triple
T4458857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maihaugen open-air museum |
E98199
|
entity |
| Predicate | significantBuildingCount |
P11484
|
FINISHED |
| Object | over 200 historic buildings |
—
|
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: over 200 historic buildings | Statement: [Maihaugen open-air museum, significantBuildingCount, over 200 historic buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantBuildingCount Context triple: [Maihaugen open-air museum, significantBuildingCount, over 200 historic buildings]
-
A.
significantBuilding
Indicates that a building holds notable importance, prominence, or special status within a particular context (e.g., historical, cultural, architectural, or functional).
-
B.
numberOfBuildings
chosen
Indicates the total count of buildings associated with a given entity or within a specified context.
-
C.
towerCount
Indicates the number of towers associated with or present in a given entity or context.
-
D.
buildingNamed
Indicates that a particular building is known or referred to by a specified name.
-
E.
buildingHeight
Indicates the vertical extent or height measurement of a building.
- 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3567184f481908a2787e4ac9bb345 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.