Triple
T38035804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rostov the Great |
E949347
|
entity |
| Predicate | hasBellCastingTradition |
P19423
|
FINISHED |
| Object | Rostov bells |
—
|
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: Rostov bells | Statement: [Rostov the Great, hasBellCastingTradition, Rostov bells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBellCastingTradition Context triple: [Rostov the Great, hasBellCastingTradition, Rostov bells]
-
A.
hasTraditionIn
chosen
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
B.
hasBellsOrigin
Indicates that something originates from, or has its source in, bells.
-
C.
hasBellChamber
Indicates that an entity possesses or includes a bell chamber as one of its structural or functional components.
-
D.
hasStageTradition
Indicates that an entity is associated with, follows, or embodies a particular stage or theatrical performance tradition.
-
E.
hasWinningTradition
Indicates that an entity (such as a team or organization) is characterized by a consistent history of success or victories in its competitive activities.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:20 p.m.