Triple
T72652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cupressaceae |
E1453
|
entity |
| Predicate | hasChromosomeType |
P4612
|
FINISHED |
| Object | haploid chromosome number typically n=11 |
—
|
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: haploid chromosome number typically n=11 | Statement: [Cupressaceae, hasChromosomeType, haploid chromosome number typically n=11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChromosomeType Context triple: [Cupressaceae, hasChromosomeType, haploid chromosome number typically n=11]
-
A.
hasSegmentType
Indicates that an entity is associated with, or classified by, a particular type or category of segment within a larger structure or sequence.
-
B.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
C.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
D.
hasNodeType
Indicates that an entity is associated with, or classified as, a specific type of node within a structured system or model.
-
E.
hasTypeName
Indicates that an entity is associated with a specific type name used to classify or identify its kind.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a252201fa481908e30791954119c17 |
completed | Feb. 28, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69a24eacfdc481909e9ff99752fd42bf |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a2521ed5088190bbdfd22164bb4d94 |
completed | Feb. 28, 2026, 2:25 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.