Triple
T11467056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pXO2 |
E271804
|
entity |
| Predicate | lossOf |
P59430
|
FINISHED |
| Object | results in acapsular phenotype |
—
|
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: results in acapsular phenotype | Statement: [pXO2, lossOf, results in acapsular phenotype]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lossOf Context triple: [pXO2, lossOf, results in acapsular phenotype]
-
A.
causedLossOf
chosen
Indicates that one entity brought about or was responsible for another entity experiencing a loss.
-
B.
lostWith
Indicates that one entity experienced a loss or defeat in conjunction with, or as part of the same side/team as, another entity.
-
C.
lost
Indicates that an entity no longer possesses or has been deprived of another entity it previously had.
-
D.
lostDuring
Indicates that something ceased to be in possession or was no longer retained while a particular event, process, or time period was occurring.
-
E.
lostSupportOf
Indicates that one entity no longer has the backing, approval, or endorsement of another entity that previously supported it.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f5eb988190b309b8e309f6d1a5 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.