Triple
T19555169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gokstad Mound |
E489287
|
entity |
| Predicate | foundHumanRemains |
P92116
|
FINISHED |
| Object | male individual |
—
|
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: male individual | Statement: [Gokstad Mound, foundHumanRemains, male individual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundHumanRemains Context triple: [Gokstad Mound, foundHumanRemains, male individual]
-
A.
numberOfUnidentifiedRemains
Indicates the count of human remains that have not yet been identified in a given context or case.
-
B.
discoveredRemainsIn
chosen
Indicates that one entity found or uncovered the physical remains of another entity at a specific location.
-
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.
finalDispositionOfRemains
Indicates the relationship specifying how a person's physical remains are ultimately handled, treated, or placed after death.
-
E.
bodiesExhumed
Indicates that previously buried bodies have been dug up and removed from their place of interment.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d335f888190abfc5ba974d3c65e |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.