Triple
T31225453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet T-35 heavy tank |
E796121
|
entity |
| Predicate | notableSurvivorLocation |
P207378
|
FINISHED |
| Object | Kubinka Tank Museum |
E1784477
|
NE 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: Kubinka Tank Museum | Statement: [Soviet T-35 heavy tank, notableSurvivorLocation, Kubinka Tank Museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSurvivorLocation Context triple: [Soviet T-35 heavy tank, notableSurvivorLocation, Kubinka Tank Museum]
-
A.
notableSanctuaryLocation
Indicates that a location is recognized as a significant or distinguished sanctuary site for the associated entity.
-
B.
notableGameLocation
Indicates that a particular place is recognized as a significant or prominent location within a game.
-
C.
notableExpeditionLocation
Indicates that a location is a significant or primary place associated with a particular expedition.
-
D.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
E.
rescuedLocation
Indicates the place where a rescue action occurred or from which someone or something was rescued.
- F. None of above. chosen
Provenance (5 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a296bdfa2f88190a787895f93eaee6d |
completed | June 10, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:10 p.m.