Triple
T1526322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo sapiens |
E32342
|
entity |
| Predicate | hasGenomeType |
P29824
|
FINISHED |
| Object | diploid |
—
|
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: diploid | Statement: [Homo sapiens, hasGenomeType, diploid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenomeType Context triple: [Homo sapiens, hasGenomeType, diploid]
-
A.
hasChromosomeType
Indicates a relationship where an entity is associated with or characterized by a specific type or category of chromosome.
-
B.
hasTypeGenus
Indicates that one entity is the type genus that formally defines or represents the taxonomic group of the other entity.
-
C.
hasGenus
Indicates that one entity belongs to, or is classified under, the biological genus represented by the other entity.
-
D.
genomeSequenced
Indicates that the complete DNA sequence of an organism’s genome has been determined and recorded.
-
E.
guthrieClassification
Indicates a categorization relationship where an entity is assigned a class or type according to the Guthrie classification system.
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a933ddc5a881909cdf503f2bc29bd4 |
completed | March 5, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69a907ae8f688190ad9000ea1e018585 |
completed | March 5, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_69a933dce3488190b20f0e3d37d16371 |
completed | March 5, 2026, 7:42 a.m. |
Created at: March 4, 2026, 7:26 p.m.