Triple
T28619205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IDXGIFactory |
E724339
|
entity |
| Predicate | uuid |
P163549
|
FINISHED |
| Object | 7b7166ec-21c7-44ae-b21a-c9ae321ae369 |
—
|
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: 7b7166ec-21c7-44ae-b21a-c9ae321ae369 | Statement: [IDXGIFactory, uuid, 7b7166ec-21c7-44ae-b21a-c9ae321ae369]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uuid Context triple: [IDXGIFactory, uuid, 7b7166ec-21c7-44ae-b21a-c9ae321ae369]
-
A.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
B.
guidType
Indicates that one entity specifies the type or category associated with a given globally unique identifier (GUID).
-
C.
hasGuid
chosen
Indicates that an entity is associated with a specific globally unique identifier (GUID) that uniquely distinguishes it from all other entities.
-
D.
GNDID
Indicates a standardized authority identifier linking an entity to its unique record in the Gemeinsame Normdatei (GND) authority file.
-
E.
URN
Indicates a relationship where an entity is identified or referenced by a Uniform Resource Name (URN), serving as a persistent, location-independent identifier.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:32 a.m.