Triple
T29852969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | blue flower |
E758110
|
entity |
| Predicate | firstMajorUseIn |
P115643
|
FINISHED |
| Object | Heinrich von Ofterdingen |
—
|
NE NERFINISHED |
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: Heinrich von Ofterdingen | Statement: [blue flower, firstMajorUseIn, Heinrich von Ofterdingen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorUseIn Context triple: [blue flower, firstMajorUseIn, Heinrich von Ofterdingen]
-
A.
firstProminentUse
chosen
Indicates the earliest notable or widely recognized instance in which something was used in a significant or influential way.
-
B.
firstMajorUseYear
Indicates the calendar year in which something was first put into major or primary use.
-
C.
firstHistoricalUse
Indicates that the subject entity represents the earliest known or recorded instance of the object entity being used or occurring in history.
-
D.
firstWidelyUsedFor
Indicates that something was the earliest instance to be broadly adopted or commonly used for a particular purpose or application.
-
E.
firstOfficialUse
Indicates the earliest point in time when something was formally or officially put into use.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a0141fceb908190863778741bd4487d |
completed | May 11, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_6a0141a9628c819090c0b24ce052a2fb |
completed | May 11, 2026, 2:40 a.m. |
Created at: April 29, 2026, 5:45 p.m.