Triple
T3300330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pummerin bell |
E69313
|
entity |
| Predicate | recastFrom |
P29172
|
FINISHED |
| Object | metal of the original Pummerin |
—
|
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: metal of the original Pummerin | Statement: [Pummerin bell, recastFrom, metal of the original Pummerin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recastFrom Context triple: [Pummerin bell, recastFrom, metal of the original Pummerin]
-
A.
recastBy
Indicates that an existing role, character, or part has been newly assigned to a different performer or entity than before.
-
B.
castFrom
chosen
Indicates that one entity is transformed or converted from another, typically changing its type or representation while preserving its underlying value or identity.
-
C.
reconstructedAs
Indicates that one entity has been rebuilt, recreated, or inferred based on evidence, models, or partial information from another entity.
-
D.
reconstructionFor
Indicates that one entity serves as a reconstruction, restoration, or rebuilt version of another entity.
-
E.
recastInYear
Indicates that an existing work, role, or production was cast again with different performers in a specified year.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a66fcc819093931fe7a6507723 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.