Triple
T29347710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oculist Witnesses |
E744215
|
entity |
| Predicate | locatedWithinComposition |
P138756
|
FINISHED |
| Object | upper register of The Large Glass |
—
|
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: upper register of The Large Glass | Statement: [Oculist Witnesses, locatedWithinComposition, upper register of The Large Glass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedWithinComposition Context triple: [Oculist Witnesses, locatedWithinComposition, upper register of The Large Glass]
-
A.
isComposedIn
Indicates that something is created, written, or formed within a particular context, medium, or framework.
-
B.
partOfComposition
chosen
Indicates that one entity is a component, section, or constituent element within a larger composite whole represented by another entity.
-
C.
placeOfComposition
Indicates the location where a work was created or composed.
-
D.
possiblePlaceOfComposition
Indicates that a location is a plausible or hypothesized place where a work was composed.
-
E.
contextOfComposition
Indicates the situational, cultural, or environmental circumstances in which a composition or work was created.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
Created at: April 28, 2026, 2:03 p.m.