Triple
T110659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roughing It |
E2240
|
entity |
| Predicate | firstEditionPages |
P1468
|
FINISHED |
| Object | ~591 |
—
|
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: ~591 | Statement: [Roughing It, firstEditionPages, ~591]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEditionPages Context triple: [Roughing It, firstEditionPages, ~591]
-
A.
firstEditionPrintRun
Indicates the initial quantity of copies produced when a work is printed in its first published edition.
-
B.
firstEditionSoldOutTime
Indicates the point in time at which the first edition of an item became completely sold out.
-
C.
pages
chosen
Indicates that one entity consists of or contains a certain number of pages, or that a specific page-related attribute is associated with it.
-
D.
notableEdition
Indicates that a particular edition or version of a work is especially significant or noteworthy in relation to that work.
-
E.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258b58efc8190959c86f73d67b744 |
completed | Feb. 28, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69a25641058c8190b5b64509b35d8176 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.