Triple
T10124761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Het Behouden Huys |
E226181
|
entity |
| Predicate | discoveredRemainsIn |
P92116
|
FINISHED |
| Object | 1871 |
—
|
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: 1871 | Statement: [Het Behouden Huys, discoveredRemainsIn, 1871]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredRemainsIn Context triple: [Het Behouden Huys, discoveredRemainsIn, 1871]
-
A.
hasBuriedRemains
Indicates that one entity contains or is the location of the buried remains of another entity.
-
B.
tombDiscovered
Indicates that a tomb has been found or uncovered, typically as the result of exploration, excavation, or chance discovery.
-
C.
rediscoveryOfRemains
Indicates the event or relationship in which previously discovered remains are found, identified, or brought to attention again after having been lost, forgotten, or overlooked.
-
D.
culturalRemains
Indicates that one entity consists of or contains physical or material traces left by a culture, such as artifacts, structures, or other archaeological evidence.
-
E.
relicsLocatedIn
Indicates that certain relics are situated, stored, or found within a specific location.
- F. None of above. chosen
Provenance (4 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2ebe4548190a484c145639d92f0 |
completed | April 2, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:05 p.m.