Triple
T22111943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlottenlund |
E546438
|
entity |
| Predicate | palaceOriginalFunction |
P45592
|
FINISHED |
| Object | royal country residence |
—
|
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 residence | Statement: [Charlottenlund, palaceOriginalFunction, royal country residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: palaceOriginalFunction Context triple: [Charlottenlund, palaceOriginalFunction, royal country residence]
-
A.
palace
Indicates that an entity is a palace, i.e., a grand official residence typically used by royalty or high-ranking authorities.
-
B.
royalPalaceFormerFunction
chosen
Indicates the previous primary role or use that a royal palace served before its current function.
-
C.
functionRelativeToPalace
Indicates that an entity has a role, purpose, or operational function defined in relation to a specific palace.
-
D.
PalaceHouseUse
Indicates a relationship where a palace is used, occupied, or functionally employed as a house or residence.
-
E.
associatedWithPalace
Indicates a relationship where an entity has a connection, link, or involvement with a palace, such as through location, function, ownership, or affiliation.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12949cc7881908898ca7dc130f57f |
completed | April 28, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.