Triple
T16369899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Olive Tree |
E397536
|
entity |
| Predicate | hasCoverMotif |
P50487
|
FINISHED |
| Object | Mediterranean house |
—
|
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: Mediterranean house | Statement: [The Olive Tree, hasCoverMotif, Mediterranean house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoverMotif Context triple: [The Olive Tree, hasCoverMotif, Mediterranean house]
-
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.
hasClosingMotif
Indicates that one entity features or is associated with a recurring thematic or structural pattern used at the end or conclusion of another entity.
-
C.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
D.
containsCoverOf
Indicates that one entity includes within it a cover or covering representation of another entity.
-
E.
hasCoverName
Indicates that one entity uses or is known by an alternative, often secret or assumed, name in relation to another entity or context.
- 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_69e2ff414d808190beae2ff162e430f8 |
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.