Triple
T11949557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ring and the Book |
E284391
|
entity |
| Predicate | sourceMaterialLocation |
P46735
|
FINISHED |
| Object | a bookstall in Florence |
—
|
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: a bookstall in Florence | Statement: [The Ring and the Book, sourceMaterialLocation, a bookstall in Florence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceMaterialLocation Context triple: [The Ring and the Book, sourceMaterialLocation, a bookstall in Florence]
-
A.
sourceMaterialType
Indicates the type or category of material from which something originates or is derived.
-
B.
materialSource
Indicates that one entity serves as the origin or provider of the material or substance used by another entity.
-
C.
hasSourceMaterial
chosen
Indicates that something is derived from, based on, or created using a particular source material.
-
D.
sourceMaterialTreatment
Indicates how the source material has been processed, altered, or treated (e.g., chemically, physically, or mechanically) before or during its use in a given context.
-
E.
sourceLocatedOn
Indicates that the source entity is physically situated on the surface or area of the target 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90346825c8190ab4482a1fc8eed56 |
completed | April 10, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.