Triple
T33548746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mrs. Joe Gargery |
E859276
|
entity |
| Predicate | theTicklerDescription |
P67296
|
FINISHED |
| Object | a wax-ended cane used to beat Pip |
—
|
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: a wax-ended cane used to beat Pip | Statement: [Mrs. Joe Gargery, theTicklerDescription, a wax-ended cane used to beat Pip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theTicklerDescription Context triple: [Mrs. Joe Gargery, theTicklerDescription, a wax-ended cane used to beat Pip]
-
A.
tickerFor
Indicates that one entity is the stock ticker symbol used to uniquely identify another entity (typically a publicly traded company or security) in financial markets.
-
B.
trigger
Indicates that one entity causes or initiates an event, state, or action in another entity or system.
-
C.
tells
Indicates that one entity communicates information, a message, or a story to another entity.
-
D.
describes
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
E.
toolDescribed
chosen
Indicates that one entity provides a description or explanation of a tool associated with another entity.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f70c17d88190aa74afc2dd2a0467 |
completed | May 3, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:39 a.m.