Triple
T2719672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lupinus angustifolius |
E60051
|
entity |
| Predicate | flowerArrangement |
P1351
|
FINISHED |
| Object | terminal racemes |
—
|
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: terminal racemes | Statement: [Lupinus angustifolius, flowerArrangement, terminal racemes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowerArrangement Context triple: [Lupinus angustifolius, flowerArrangement, terminal racemes]
-
A.
flowerType
Indicates the specific kind or category of flower associated with an entity.
-
B.
flowerPosition
Indicates the spatial location or arrangement of a flower relative to a reference object or coordinate system.
-
C.
flowerStructure
chosen
Indicates the structural characteristics or organization of a flower, such as the arrangement and form of its parts.
-
D.
arrangementFeatures
Indicates that one entity specifies or characterizes the structural or compositional features of an arrangement involving another entity.
-
E.
arrangement
Indicates a relationship where entities are organized, ordered, or positioned in a particular configuration or sequence relative to one another.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaaee104819085966bc54d5da9c0 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8240920819087a812d816a55edb |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.