Triple
T33292324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VKORC1 |
E852347
|
entity |
| Predicate | requiredForActivationOf |
P104948
|
FINISHED |
| Object | prothrombin (factor II) |
—
|
NE NERFINISHED |
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: prothrombin (factor II) | Statement: [VKORC1, requiredForActivationOf, prothrombin (factor II)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredForActivationOf Context triple: [VKORC1, requiredForActivationOf, prothrombin (factor II)]
-
A.
activationRequirement
chosen
Indicates the conditions or prerequisites that must be satisfied for an entity, process, or function to become active or operational.
-
B.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
-
C.
ordinationRequiredFor
Indicates that a formal ordination is a necessary prerequisite for performing or holding the specified role, function, or office.
-
D.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
-
E.
requiresRegistrationFor
Indicates that one entity can only access, use, or participate in another entity if a prior registration process has been completed.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: May 1, 2026, 1:33 a.m.