Triple
T26249376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Woodhouse |
E656537
|
entity |
| Predicate | appearsInChapterCount |
P2946
|
FINISHED |
| Object | multiple chapters of Emma |
—
|
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: multiple chapters of Emma | Statement: [Mr. Woodhouse, appearsInChapterCount, multiple chapters of Emma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInChapterCount Context triple: [Mr. Woodhouse, appearsInChapterCount, multiple chapters of Emma]
-
A.
numberOfChapters
chosen
Indicates the total count of chapters associated with a given entity.
-
B.
appearsInBookNumber
Indicates that an entity is featured or mentioned in a specific book identified by its number within a series or collection.
-
C.
containsChapter
Indicates that one entity (typically a larger work or document) includes another entity as a chapter within its structure.
-
D.
gameChapter
Indicates that one entity is a chapter, level, or segment that forms part of the progression or structure of a game.
-
E.
chapterNumber
Indicates the specific ordinal position a chapter occupies within a larger ordered work, such as a book or document.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 26, 2026, 9:06 p.m.