Triple
T15884187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4 Wheat. 518 |
E385147
|
entity |
| Predicate | pageNumber |
P120918
|
FINISHED |
| Object | 518 |
—
|
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: 518 | Statement: [4 Wheat. 518, pageNumber, 518]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pageNumber Context triple: [4 Wheat. 518, pageNumber, 518]
-
A.
pageSize
Indicates the size or amount of content (such as items, records, or data) that is included or displayed on a single page.
-
B.
pages
Indicates that one entity consists of or contains a certain number of pages, or that a specific page-related attribute is associated with it.
-
C.
pageIndexNotation
Indicates that a specific notation or label is used to identify the index or position of a page within an ordered sequence of pages.
-
D.
codePageNumber
Indicates the specific page number within a code document or code listing where something is located or referenced.
-
E.
pageE2
Indicates that one entity is the second page (or page-level element 2) associated with another entity, typically in an ordered sequence of pages.
- F. None of above. chosen
Provenance (4 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:51 a.m.