Triple
T27762733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flash, Bang, Wallop! |
E701510
|
entity |
| Predicate | isSignatureNumberOf |
P163951
|
FINISHED |
| Object | Half a Sixpence |
—
|
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: Half a Sixpence | Statement: [Flash, Bang, Wallop!, isSignatureNumberOf, Half a Sixpence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSignatureNumberOf Context triple: [Flash, Bang, Wallop!, isSignatureNumberOf, Half a Sixpence]
-
A.
signatureNumber
Indicates the identifying number assigned to a specific signature within a document or signing process.
-
B.
isSignatureHitOf
Indicates that one hit or impact is the characteristic or defining strike associated with a particular entity, event, or performance.
-
C.
isSigned
Indicates that an entity has been formally endorsed or authenticated through a signature or signing action.
-
D.
estimatedNumberOfSignatures
Indicates the approximate count of signatures associated with or required for a given item, action, or agreement.
-
E.
hasSignatureBit
Indicates that an entity possesses a specific bit or flag used to represent a signature or signed status in a data structure or encoding.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 4:28 p.m.