Triple
T29041252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross-Community Patient Discovery |
E738001
|
entity |
| Predicate | hasTransactionId |
P53608
|
FINISHED |
| Object | ITI-55 |
—
|
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: ITI-55 | Statement: [Cross-Community Patient Discovery, hasTransactionId, ITI-55]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransactionId Context triple: [Cross-Community Patient Discovery, hasTransactionId, ITI-55]
-
A.
usesTransaction
Indicates that one entity conducts or performs an action by means of a specific transaction or transactional process.
-
B.
hasTransfer
Indicates a relationship where something is moved or conveyed from one entity or location to another.
-
C.
hasReferenceID
chosen
Indicates that an entity is associated with a specific reference identifier used to uniquely track or distinguish it.
-
D.
supportsTransactions
Indicates that one entity provides the capability for another entity to perform or manage transactions reliably.
-
E.
underlyingTransaction
Indicates that one transaction serves as the basis, source, or supporting context for another related transaction.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 28, 2026, 10:02 a.m.