Triple
T5622535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adonis |
E147641
|
entity |
| Predicate | bodyTransformedInto |
P65473
|
FINISHED |
| Object | anemone flower |
—
|
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: anemone flower | Statement: [Adonis, bodyTransformedInto, anemone flower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyTransformedInto Context triple: [Adonis, bodyTransformedInto, anemone flower]
-
A.
transformedDuring
Indicates that an entity undergoes a change in form, state, or structure within the duration of a specified event or process.
-
B.
crownTransformedInto
Indicates that a crown undergoes a change of state or form, resulting in it becoming a different specified object or condition.
-
C.
movementTransformed
Indicates that an entity’s movement has been altered or converted from one form, state, or pattern into another.
-
D.
bodyFusedWith
Indicates that two or more bodies or physical structures are joined together into a single, continuous unit.
-
E.
regionTransformed
Indicates that one region has been changed or converted into another region through some transformation process.
- F. None of above. chosen
Provenance (4 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c022133eec819086acb04864dde5ee |
completed | March 22, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f40df64819089a659ea00a835ef |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:40 p.m.