Triple
T17531440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collegiate Church of St. Servatius |
E426942
|
entity |
| Predicate | hasCryptBurials |
P62966
|
FINISHED |
| Object | members of the Ottonian dynasty |
—
|
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: members of the Ottonian dynasty | Statement: [Collegiate Church of St. Servatius, hasCryptBurials, members of the Ottonian dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCryptBurials Context triple: [Collegiate Church of St. Servatius, hasCryptBurials, members of the Ottonian dynasty]
-
A.
hasCrypt
Indicates that one entity possesses, contains, or is associated with a crypt belonging to or located within it.
-
B.
hasBuriedRemains
Indicates that one entity contains or is the location of the buried remains of another entity.
-
C.
hasMultipleBurials
Indicates that a single grave or burial site contains the remains of more than one individual.
-
D.
hasBurialVault
Indicates that an entity possesses or is associated with a specific burial vault used for interment or storage of remains.
-
E.
hasBurialsOf
chosen
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e453688950819098162d853cd2674e |
completed | April 19, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.