Triple
T15799497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xanthorhiza |
E383061
|
entity |
| Predicate | rootUse |
P120062
|
FINISHED |
| Object | dye-producing |
—
|
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: dye-producing | Statement: [Xanthorhiza, rootUse, dye-producing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rootUse Context triple: [Xanthorhiza, rootUse, dye-producing]
-
A.
rootSystem
Indicates that one entity is the primary or foundational source from which another entity originates, grows, or is structurally anchored.
-
B.
usesRepository
Indicates that one entity relies on, accesses, or interacts with a particular repository as a resource or data source.
-
C.
denUse
Indicates that an entity uses or makes use of a particular den (or designated shelter/space) for its activities or habitation.
-
D.
originUse
Indicates that one entity is used as the original source, basis, or starting point for the creation, derivation, or use of another entity.
-
E.
rootPresence
Indicates that an entity possesses, exhibits, or contains a root or root-like structure.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4e00d348190bc98917c4098ec2f |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e006b17f7881908b8c7a37f0af4581 |
completed | April 15, 2026, 9:44 p.m. |
Created at: April 10, 2026, 4:48 a.m.