Triple
T28872363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IHE XCA |
E732172
|
entity |
| Predicate | versionedIn |
P24987
|
FINISHED |
| Object | IHE ITI Technical Framework Volume 1 |
—
|
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: IHE ITI Technical Framework Volume 1 | Statement: [IHE XCA, versionedIn, IHE ITI Technical Framework Volume 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: versionedIn Context triple: [IHE XCA, versionedIn, IHE ITI Technical Framework Volume 1]
-
A.
versionedAs
Indicates that one entity exists as a specific version or revision of another entity.
-
B.
hasVersionIn
chosen
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
C.
isVersionOf
Indicates that one entity is a particular version, edition, or variant derived from another entity.
-
D.
versionOf
Indicates that one entity is a specific form, edition, or variant derived from or corresponding to another entity.
-
E.
historicalVersion
Indicates that one entity represents an earlier or past version in the history or evolution of 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 7:34 a.m.