Triple
T9216281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Echinacea |
E221247
|
entity |
| Predicate | usedPart |
P57217
|
FINISHED |
| Object | roots |
—
|
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: roots | Statement: [Echinacea, usedPart, roots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPart Context triple: [Echinacea, usedPart, roots]
-
A.
partUsed
chosen
Indicates that one entity is a component or part that is utilized in the construction, operation, or composition of another entity.
-
B.
usedComponent
Indicates that one entity has employed or incorporated another entity as a component in its structure, function, or operation.
-
C.
usedParticle
Indicates that one entity employs or applies a particular particle (e.g., subatomic, linguistic, or material) in some process, context, or construction involving another entity.
-
D.
usedItem
Indicates that an entity has utilized or employed a particular item for some purpose.
-
E.
hasPartUsed
Indicates that an entity utilizes another entity as a component or constituent part in its structure, function, or operation.
- 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda096358819096d4e790da057512 |
completed | April 1, 2026, 8:40 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:27 p.m.