Triple
T16369677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Orchid House |
E397530
|
entity |
| Predicate | hasCoverElement |
P50487
|
FINISHED |
| Object | orchid imagery |
—
|
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: orchid imagery | Statement: [The Orchid House, hasCoverElement, orchid imagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoverElement Context triple: [The Orchid House, hasCoverElement, orchid imagery]
-
A.
hasCoverFeature
chosen
Indicates that one entity serves as a prominent or featured element on the cover of another entity (such as a publication, product, or media item).
-
B.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
C.
hasCoverName
Indicates that one entity uses or is known by an alternative, often secret or assumed, name in relation to another entity or context.
-
D.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
-
E.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff4021e88190ad093bab74cf82a4 |
completed | April 18, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.