Triple
T11074672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riabni |
E261832
|
entity |
| Predicate | hasSpeciesOrigin |
P18418
|
FINISHED |
| Object | human-mouse chimeric |
—
|
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: human-mouse chimeric | Statement: [Riabni, hasSpeciesOrigin, human-mouse chimeric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeciesOrigin Context triple: [Riabni, hasSpeciesOrigin, human-mouse chimeric]
-
A.
originSpecies
chosen
Indicates that one entity is the original or source species from which another entity is derived, evolved, or produced.
-
B.
hasBreedOrigin
Indicates that an animal breed originates from or was first developed in a specified geographic location or cultural region.
-
C.
speciesOrigin
Indicates the place, environment, or source from which a species originally arose or evolved.
-
D.
biologicalOrigin
Indicates that one entity originates from, is derived from, or is produced by a biological source or organism in relation to another entity.
-
E.
hasFlagshipSpecies
Indicates that one entity (typically a site, region, or conservation program) is associated with or represented by a particular flagship species used to promote awareness or protection.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7994efb608190a81bc8c4d16ddbd0 |
completed | April 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.