Triple
T28938934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTT |
E730391
|
entity |
| Predicate | hasReferenceSequence |
P200662
|
FINISHED |
| Object | NM_002111 |
—
|
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: NM_002111 | Statement: [HTT, hasReferenceSequence, NM_002111]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReferenceSequence Context triple: [HTT, hasReferenceSequence, NM_002111]
-
A.
hasConsensusSequence
Indicates that there is an agreed-upon or representative sequence associated with the entity, typically summarizing the most common or characteristic form among multiple sequences.
-
B.
hasReferenceID
Indicates that an entity is associated with a specific reference identifier used to uniquely track or distinguish it.
-
C.
hasReferences
Indicates that one entity cites, points to, or relies on another entity as a reference or source.
-
D.
hasCharacterSequence
Indicates that one entity contains, exhibits, or follows a specific ordered sequence of characters.
-
E.
hasSequencePosition
Indicates that an element occupies a specific position or order within a sequence.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69ff9e90b5248190bdd8d13f966b63e1 |
completed | May 9, 2026, 8:52 p.m. |
Created at: April 28, 2026, 8:34 a.m.