Triple
T21933770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ex Libris: 100+ Books to Read and Reread |
E541635
|
entity |
| Predicate | numberOfBooksDiscussed |
P5481
|
FINISHED |
| Object | more than 100 |
—
|
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: more than 100 | Statement: [Ex Libris: 100+ Books to Read and Reread, numberOfBooksDiscussed, more than 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfBooksDiscussed Context triple: [Ex Libris: 100+ Books to Read and Reread, numberOfBooksDiscussed, more than 100]
-
A.
numberOfBooks
chosen
Indicates the quantity of books associated with a given entity.
-
B.
numberOfDialogues
Indicates the total count of dialogues associated with or occurring between the referenced entities.
-
C.
numberOfCompletedBooks
Indicates the total count of books that an entity has finished reading or completing.
-
D.
intendedNumberOfBooks
Indicates the number of books that an agent plans or aims to have, produce, read, or otherwise be associated with, as opposed to the number actually realized.
-
E.
numberOfWorks
Indicates the total count of works associated with a given entity.
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12400a1248190b3f8f27f2aa4a858 |
completed | April 28, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:49 p.m.