Triple
T27210268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botik Museum of Peter the Great |
E683978
|
entity |
| Predicate | hasObjectNickname |
P109144
|
FINISHED |
| Object | grandfather of the Russian Navy |
—
|
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: grandfather of the Russian Navy | Statement: [Botik Museum of Peter the Great, hasObjectNickname, grandfather of the Russian Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObjectNickname Context triple: [Botik Museum of Peter the Great, hasObjectNickname, grandfather of the Russian Navy]
-
A.
hasNicknameStatus
Indicates that an entity holds a particular status or classification specifically related to its nickname.
-
B.
hasNicknameForm
Indicates that one entity is a nickname or informal variant form of another entity’s name.
-
C.
nicknameOfObject
chosen
Indicates that one entity is used as an informal or alternative name (nickname) for another entity.
-
D.
hasShapeNickname
Indicates that an entity is associated with an informal or colloquial nickname referring to its shape.
-
E.
hasNicknamedFeature
Indicates that an entity possesses a feature or attribute that is commonly referred to by a specific nickname.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625e8342c8190a809bfb169967a89 |
completed | May 2, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 9:39 a.m.