Triple
T21486869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Leaping Horse |
E530137
|
entity |
| Predicate | hasCatalogueStatus |
P10583
|
FINISHED |
| Object | major work in Constable's oeuvre |
—
|
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: major work in Constable's oeuvre | Statement: [The Leaping Horse, hasCatalogueStatus, major work in Constable's oeuvre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatalogueStatus Context triple: [The Leaping Horse, hasCatalogueStatus, major work in Constable's oeuvre]
-
A.
catalogueStatus
chosen
Indicates the current state or condition of an item within a catalogue or listing system (e.g., active, inactive, pending).
-
B.
hasCatalogueContext
Indicates that something is associated with, or occurs within, a specific catalogue-related context or framework.
-
C.
hasOnlineCatalog
Indicates that an entity provides a catalog of its items or offerings that is accessible via the internet.
-
D.
hasCatalogueSize
Indicates that an entity possesses a catalogue containing a specified number of items or entries.
-
E.
hasCatalogView
Indicates that an entity is associated with a particular way or mode of viewing or presenting a catalog.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea37e25c81909ae185fcab19bc4b |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:22 p.m.