Triple
T15152500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornelius van Baerle |
E361978
|
entity |
| Predicate | centralObjectOfDesire |
P64674
|
FINISHED |
| Object | a unique black tulip |
—
|
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 unique black tulip | Statement: [Cornelius van Baerle, centralObjectOfDesire, a unique black tulip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralObjectOfDesire Context triple: [Cornelius van Baerle, centralObjectOfDesire, a unique black tulip]
-
A.
describesDesireFor
Indicates that one entity expresses or conveys a wish, longing, or aspiration directed toward another entity or outcome.
-
B.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
C.
secondaryGoal
Indicates that something serves as a subordinate or supporting objective in addition to a primary goal.
-
D.
primaryUnionObjective
Indicates the main goal or purpose that a union seeks to achieve in its activities or negotiations.
-
E.
centralQuest
Indicates that an action, objective, or storyline serves as the primary or main quest within a larger narrative or mission structure.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00609040081908c849475a2fa6443 |
completed | April 15, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:07 a.m.