Triple
T18346290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great George bell |
E439546
|
entity |
| Predicate | typeOfRinging |
P47851
|
FINISHED |
| Object | full-circle swinging bell |
—
|
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: full-circle swinging bell | Statement: [Great George bell, typeOfRinging, full-circle swinging bell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRinging Context triple: [Great George bell, typeOfRinging, full-circle swinging bell]
-
A.
ringingMethod
chosen
Indicates that one entity uses or is associated with a specific method or pattern for ringing (such as in bell-ringing or similar signaling activities).
-
B.
numberOfRings
Indicates the quantity of rings associated with an entity.
-
C.
usesRingingVoltage
Indicates that one entity applies or relies on a specific ringing voltage signal to activate or operate another entity.
-
D.
hasRingAnnouncer
Indicates that an event, typically a combat or sports match, is associated with a specific ring announcer who introduces participants and makes formal announcements.
-
E.
ringType
Indicates the specific kind or category of ring associated with an entity or relationship.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e514f4740c8190b70ba48a4232953e |
completed | April 19, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.