Triple
T25048661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr Tompkins in Wonderland |
E627313
|
entity |
| Predicate | laterCombinedIn |
P70673
|
FINISHED |
| Object | Mr Tompkins in Paperback |
—
|
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: Mr Tompkins in Paperback | Statement: [Mr Tompkins in Wonderland, laterCombinedIn, Mr Tompkins in Paperback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCombinedIn Context triple: [Mr Tompkins in Wonderland, laterCombinedIn, Mr Tompkins in Paperback]
-
A.
laterCombination
Indicates that one entity is a combination or composite that occurs after, or is formed subsequent to, another entity or state.
-
B.
laterComplementedBy
Indicates that an earlier entity is subsequently supplemented, enhanced, or completed by a later entity.
-
C.
combinedIn
chosen
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
D.
laterExtendedIn
Indicates that an existing entity (such as a work, version, or specification) was subsequently expanded, updated, or built upon by a later entity.
-
E.
laterMergedWith
Indicates that one entity was combined into and became part of another entity at a subsequent point in time.
- 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 6:08 a.m.