Triple
T28830851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canis lycaon |
E728043
|
entity |
| Predicate | hybridizationOccursWith |
P39441
|
FINISHED |
| Object | Canis lupus |
—
|
NE NERFINISHED |
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: Canis lupus | Statement: [Canis lycaon, hybridizationOccursWith, Canis lupus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hybridizationOccursWith Context triple: [Canis lycaon, hybridizationOccursWith, Canis lupus]
-
A.
hasHybridization
chosen
Indicates that one entity participates in or results from a hybridization process involving another entity.
-
B.
hasHybridSpecies
Indicates that one entity is a hybrid species that results from the combination or crossbreeding of another entity (or entities).
-
C.
notableHybrid
Indicates that one entity is a hybrid of two or more distinct types, lineages, or categories and is recognized as notable or significant in that hybrid form.
-
D.
hasHybridUses
Indicates that an entity is used in both traditional (e.g., physical or analog) and modern or alternative (e.g., digital, renewable, or mixed-mode) ways or contexts.
-
E.
hybridName
Indicates that an entity has a designated name specifically used for a hybrid or cross-bred form derived from multiple sources.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6593ca620819080169328db2e16e9 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:37 a.m.