Triple
T1250135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warren Commission |
E26854
|
entity |
| Predicate | pagesOfReport |
P1468
|
FINISHED |
| Object | over 800 |
—
|
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: over 800 | Statement: [Warren Commission, pagesOfReport, over 800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pagesOfReport Context triple: [Warren Commission, pagesOfReport, over 800]
-
A.
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.
-
B.
hasPageCountApprox
Indicates that an entity is associated with an approximate or estimated number of pages, rather than an exact page count.
-
C.
bookChapterRange
Indicates a relationship where a specified range of chapters within a book is identified or referenced as a contiguous segment.
-
D.
firstPageInUnitedStatesReports
Indicates that a legal case or decision appears on the first page of a specified volume of the United States Reports.
-
E.
hasPage
Indicates that one entity includes, is associated with, or is documented by a specific page (such as a web page or document page).
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf84c73c8190bbb14265cd7ab6ae |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6b075881908e867c25b5080e25 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.