Triple
T3259418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosenborg Castle |
E68373
|
entity |
| Predicate | originallyBuiltAs |
P30482
|
FINISHED |
| Object | royal country summerhouse |
—
|
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: royal country summerhouse | Statement: [Rosenborg Castle, originallyBuiltAs, royal country summerhouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyBuiltAs Context triple: [Rosenborg Castle, originallyBuiltAs, royal country summerhouse]
-
A.
wasOriginallyBuiltAs
chosen
Indicates that an object or structure was initially constructed for a particular purpose, function, or role, which may differ from its current use.
-
B.
originallyBuilt
Indicates that one entity was the first or initial builder or constructor of another entity.
-
C.
originallyBuiltBy
Indicates that something was first constructed or created by a particular agent, organization, or entity.
-
D.
isBuiltFor
Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
-
E.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adafa4f40c81909adfd0f7f568e3ce |
completed | March 8, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.