Triple
T3670786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tryptophan |
E77872
|
entity |
| Predicate | hasStandardGeneticCodeNumber |
P508
|
FINISHED |
| Object | amino acid number 11 in many lists |
—
|
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: amino acid number 11 in many lists | Statement: [tryptophan, hasStandardGeneticCodeNumber, amino acid number 11 in many lists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardGeneticCodeNumber Context triple: [tryptophan, hasStandardGeneticCodeNumber, amino acid number 11 in many lists]
-
A.
hasGenomeType
Indicates that an entity possesses or is characterized by a specific type or classification of genome.
-
B.
geneticMaterial
Indicates that one entity serves as the hereditary or genetic substance (e.g., DNA or RNA) of another entity.
-
C.
geneticStatus
Indicates the genetic condition or variant state an entity has in relation to a specific gene or set of genes.
-
D.
numericCode
chosen
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
E.
estimatedNumberOfGenes
Indicates the approximate count of genes that an entity (such as an organism or genome) is believed to possess.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc42c96648190abbd5d23b25d6a6b |
completed | March 8, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69adb84a20288190a092e4a1b045fe3f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.