Triple
T3670785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tryptophan |
E77872
|
entity |
| Predicate | cannotBeSynthesizedBy |
P38827
|
FINISHED |
| Object | humans |
—
|
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: humans | Statement: [tryptophan, cannotBeSynthesizedBy, humans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotBeSynthesizedBy Context triple: [tryptophan, cannotBeSynthesizedBy, humans]
-
A.
canBeConstructedWith
Indicates that one entity can be formed, built, or assembled using another entity as material, components, or means.
-
B.
cannotBeInheritedAs
Indicates that a property, method, or characteristic of one entity is not allowed to be passed down or inherited by another entity.
-
C.
allowsSynthesisFromSources
Indicates that one entity permits the creation or production of something using specified source entities or materials.
-
D.
notDerivedFrom
chosen
Indicates that one entity is explicitly not obtained, inferred, or produced from another entity.
-
E.
notImplementedBy
Indicates that a specified functionality, specification, or feature is *not* realized or provided by the referenced entity (such as a system, component, or implementation).
- 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.