Triple
T22693140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WDR41 |
E561101
|
entity |
| Predicate | participatesInComplex |
P31120
|
FINISHED |
| Object | PIKfyve-VAC14-FIG4 complex |
—
|
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: PIKfyve-VAC14-FIG4 complex | Statement: [WDR41, participatesInComplex, PIKfyve-VAC14-FIG4 complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participatesInComplex Context triple: [WDR41, participatesInComplex, PIKfyve-VAC14-FIG4 complex]
-
A.
hasComplex
chosen
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
-
B.
requiresParticipationOf
Indicates that one entity’s occurrence, validity, or completion depends on the active involvement or participation of another entity.
-
C.
hasComplexification
Indicates that one entity is a more complex or elaborated version, form, or development of another entity.
-
D.
coParticipantIn
Indicates that two or more entities take part together as participants in the same event, activity, or situation.
-
E.
hasComplicatedRelationshipWith
Indicates that one entity is involved in a complex, often ambiguous or difficult-to-define interpersonal or relational dynamic with another entity.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789c6ae481908975b7d27e7624ac |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.