Triple
T22111959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlottenlund |
E546438
|
entity |
| Predicate | palaceLaterUse |
P45592
|
FINISHED |
| Object | research institution |
—
|
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: research institution | Statement: [Charlottenlund, palaceLaterUse, research institution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: palaceLaterUse Context triple: [Charlottenlund, palaceLaterUse, research institution]
-
A.
PalaceHouseUse
Indicates a relationship where a palace is used, occupied, or functionally employed as a house or residence.
-
B.
royalPalaceFormerFunction
chosen
Indicates the previous primary role or use that a royal palace served before its current function.
-
C.
palace
Indicates that an entity is a palace, i.e., a grand official residence typically used by royalty or high-ranking authorities.
-
D.
notUsedAsOfficialRoyalPalace
Indicates that a building or residence is not designated or employed as an official royal palace by the relevant monarchy or royal authority.
-
E.
usedAsRoyalResidenceUntil
Indicates that something served as a royal residence up to a specified point in time.
- 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.