Triple
T11823142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Household Words |
E281188
|
entity |
| Predicate | firstIssuePrice |
P4148
|
FINISHED |
| Object | two pence |
—
|
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: two pence | Statement: [Household Words, firstIssuePrice, two pence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIssuePrice Context triple: [Household Words, firstIssuePrice, two pence]
-
A.
firstIssueNumber
Indicates the issue number at which something (such as a series, feature, or character) first appeared or began.
-
B.
actualLaunchPrice
chosen
Indicates the price at which something was actually launched or first offered, as opposed to its planned or advertised launch price.
-
C.
firstOffered
Indicates that one entity was the earliest or initial provider or proposer of something to another entity or context.
-
D.
firstRelease
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
-
E.
assembledPriceAtIntroduction
Indicates the price assigned to an assembled product at the time it is first introduced or launched.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e9c50481909b2287a0b23d2094 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.