Triple
T8276088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brandeis Brief |
E193550
|
entity |
| Predicate | pagesCount |
P1468
|
FINISHED |
| Object | over 100 pages |
—
|
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 100 pages | Statement: [Brandeis Brief, pagesCount, over 100 pages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pagesCount Context triple: [Brandeis Brief, pagesCount, over 100 pages]
-
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.
pageSize
Indicates the size or amount of content (such as items, records, or data) that is included or displayed on a single page.
-
D.
codePageNumber
Indicates the specific page number within a code document or code listing where something is located or referenced.
-
E.
pageCountFirstEdition
Indicates the number of pages contained in the first edition of an item.
- 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb798d69508190b581ad8a38730175 |
completed | March 31, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.