Triple
T19744009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombyx mandarina |
E474203
|
entity |
| Predicate | isAncestralProgenitorOf |
P59558
|
FINISHED |
| Object | Bombyx mori |
—
|
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: Bombyx mori | Statement: [Bombyx mandarina, isAncestralProgenitorOf, Bombyx mori]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAncestralProgenitorOf Context triple: [Bombyx mandarina, isAncestralProgenitorOf, Bombyx mori]
-
A.
producedAncestorOf
Indicates that one entity is an ancestor of another in a production or derivation chain, having directly or indirectly produced it through intermediate steps.
-
B.
progenitorOf
chosen
Indicates that one entity is the direct biological or ancestral source (parent or originator) of another entity.
-
C.
proposesAncestor
Indicates that one entity puts forward or suggests another entity as a possible ancestor in a lineage or hierarchy.
-
D.
relationToAncestors
Indicates a familial relationship that connects an entity to one or more of its ancestors in a lineage or hierarchy.
-
E.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e652923fd48190982c51c39814fd08 |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.