Triple
T21124316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District and Circle |
E520516
|
entity |
| Predicate | hasISBNOfCollection |
P126854
|
FINISHED |
| Object | 9780571230693 |
—
|
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: 9780571230693 | Statement: [District and Circle, hasISBNOfCollection, 9780571230693]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISBNOfCollection Context triple: [District and Circle, hasISBNOfCollection, 9780571230693]
-
A.
hasISBNInCollection
chosen
Indicates that a particular ISBN is present within a specified collection of items or works.
-
B.
containsBook
Indicates that one entity (typically a container or collection) includes a specific book as part of its contents.
-
C.
bookNumberInCollection
Indicates the specific numerical position assigned to a book within a particular collection.
-
D.
hasBookSetIn
Indicates that a book’s story takes place in, or is primarily set within, a particular location.
-
E.
hasCanonicalCollectionEdition
Indicates that an entity has a specific edition that is recognized as the authoritative or standard version within a collection.
- 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72237c1a4819090987c645114d452 |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.