Triple
T6004809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C9orf72 |
E133683
|
entity |
| Predicate | locatedOnChromosome |
P68668
|
FINISHED |
| Object | chromosome 9 |
—
|
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: chromosome 9 | Statement: [C9orf72, locatedOnChromosome, chromosome 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnChromosome Context triple: [C9orf72, locatedOnChromosome, chromosome 9]
-
A.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
B.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
locatedOnBody
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
D.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
E.
sourceLocatedOn
Indicates that the source entity is physically situated on the surface or area of the target entity.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f10d18081908c351170b7f58d3d |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8c5bfc8190b986a7071d1b23e3 |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:06 p.m.