Triple
T3300327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pummerin bell |
E69313
|
entity |
| Predicate | currentVersionCastIn |
P47848
|
FINISHED |
| Object | 1951 |
—
|
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: 1951 | Statement: [Pummerin bell, currentVersionCastIn, 1951]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentVersionCastIn Context triple: [Pummerin bell, currentVersionCastIn, 1951]
-
A.
currentVersionDefinedIn
Indicates that the current or active version of an entity is specified or established within a particular source, document, or context.
-
B.
currentVersionAdopted
Indicates that a specified version is the one presently in use or officially adopted by the relevant entity or system.
-
C.
currentCoreVersionEnactedIn
Indicates that a specific version of the core (e.g., a standard, framework, or core specification) is currently in force within a given context, jurisdiction, or system.
-
D.
versionOf
Indicates that one entity is a specific form, edition, or variant derived from or corresponding to another entity.
-
E.
latestVersion
Indicates that one entity is the most recent or up-to-date version of another entity within a sequence or set of versions.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:11 p.m.