Triple
T37291343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EPAS1 |
E925672
|
entity |
| Predicate | bindsWith |
P37017
|
FINISHED |
| Object | ARNT |
—
|
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: ARNT | Statement: [EPAS1, bindsWith, ARNT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bindsWith Context triple: [EPAS1, bindsWith, ARNT]
-
A.
bindingOn
Indicates that one party is legally or formally obligated to follow, accept, or be governed by a decision, rule, or agreement established by another.
-
B.
bindsTo
chosen
Indicates that one entity physically or functionally attaches or connects to another, often with some specificity or selectivity in the interaction.
-
C.
bindingFrom
Indicates a relationship where something originates or results from a specific binding or attachment process.
-
D.
bindingAsTo
Indicates that one entity is legally or contractually binding upon another entity with respect to certain terms, obligations, or conditions.
-
E.
bindingFor
Indicates that one entity serves as the binding, constraint, or linkage mechanism that determines how another entity is associated, applied, or made effective.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.