Triple
T33316700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HKSample |
E853033
|
entity |
| Predicate | canBeQueriedBy |
P159962
|
FINISHED |
| Object | HKSampleQuery |
—
|
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: HKSampleQuery | Statement: [HKSample, canBeQueriedBy, HKSampleQuery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeQueriedBy Context triple: [HKSample, canBeQueriedBy, HKSampleQuery]
-
A.
canRetrieve
Indicates that one entity has the ability or permission to retrieve or fetch another entity or resource.
-
B.
canAsk
chosen
Indicates that one entity has the ability or permission to pose a question or make a request to another entity.
-
C.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
D.
dataAccessibleTo
Indicates that certain data can be reached, retrieved, or used by a specified entity or system.
-
E.
hasObservationAccess
Indicates that an entity is permitted to view or retrieve observations or observational data associated 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 1, 2026, 1:33 a.m.