Triple
T32390521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahlefeldt-Laurvig-Bille family |
E827657
|
entity |
| Predicate | estateAssociation |
P126569
|
FINISHED |
| Object | Egeskov Castle |
—
|
NE NERFINISHED |
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: Egeskov Castle | Statement: [Ahlefeldt-Laurvig-Bille family, estateAssociation, Egeskov Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estateAssociation Context triple: [Ahlefeldt-Laurvig-Bille family, estateAssociation, Egeskov Castle]
-
A.
estateLinkedToTitle
Indicates that a particular estate is legally or formally associated with a specific title.
-
B.
estateRole
Indicates the specific function, capacity, or responsibility an entity holds in relation to an estate (such as owner, executor, or beneficiary).
-
C.
estate
Indicates a legal or ownership relationship in which a person or entity holds rights, interests, or control over property or assets.
-
D.
estateManaged
Indicates that one entity is responsible for administering, overseeing, or handling the affairs and assets of another entity’s estate.
-
E.
realEstate
chosen
Indicates a relationship where an entity owns, manages, or is otherwise associated with real property such as land or buildings.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1d9a0848190b39120e9d669b8a5 |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:52 a.m.