Triple
T31490220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nibelung hoard |
E803385
|
entity |
| Predicate | laterPossessedBy |
P59297
|
FINISHED |
| Object | Siegfried |
—
|
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: Siegfried | Statement: [Nibelung hoard, laterPossessedBy, Siegfried]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPossessedBy Context triple: [Nibelung hoard, laterPossessedBy, Siegfried]
-
A.
possessedBy
Indicates that something is owned, controlled, or held by a particular entity.
-
B.
temporarilyPossessedBy
Indicates that an entity is in the possession or control of another entity for a limited or non-permanent period of time.
-
C.
previouslyPossessedBy
chosen
Indicates that an entity was owned or possessed by another entity at some time in the past, but is not necessarily possessed by that entity now.
-
D.
laterOccupant
Indicates that one entity occupied or held a position in a place or role after another entity had previously done so.
-
E.
laterUsurpedBy
Indicates that one entity, after some time has passed, is overthrown or replaced in power, position, or authority by another entity.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
Created at: April 30, 2026, 9:37 p.m.