Triple
T28818200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epstein–Barr virus infection |
E727688
|
entity |
| Predicate | commonSign |
P190340
|
FINISHED |
| Object | splenomegaly |
—
|
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: splenomegaly | Statement: [Epstein–Barr virus infection, commonSign, splenomegaly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonSign Context triple: [Epstein–Barr virus infection, commonSign, splenomegaly]
-
A.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
B.
commonUsers
Indicates that two or more entities share at least one user in common, such as overlapping account holders, participants, or audience members.
-
C.
commonApplication
Indicates that multiple entities share or participate in the same application, process, or usage context.
-
D.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
E.
commonLabel
Indicates that two or more entities share the same label or designation.
- F. None of above. chosen
Provenance (4 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc4b5f22c8190b8b256adbdc2570c |
completed | May 7, 2026, 4:58 p.m. |
Created at: April 28, 2026, 6:33 a.m.