Triple
T20011174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wuggly Ump |
E494591
|
entity |
| Predicate | hasPrintRunType |
P47715
|
FINISHED |
| Object | trade edition |
—
|
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: trade edition | Statement: [The Wuggly Ump, hasPrintRunType, trade edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrintRunType Context triple: [The Wuggly Ump, hasPrintRunType, trade edition]
-
A.
hasRunType
Indicates the type or category of a run associated with an entity (e.g., execution mode, run classification, or run configuration).
-
B.
printRunType
chosen
Indicates the type or mode in which a print operation or print job is executed.
-
C.
hasImprintType
Indicates that an entity (such as a publication or product) is associated with a specific type or category of imprint.
-
D.
isPrinted
Indicates that a physical copy of an item has been produced using a printing process.
-
E.
hasPrintVersion
Indicates that one entity exists or is available as a printed or physical edition of 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662362df48190abf16129eea39985 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.