Triple
T23581344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Bruce Bailey |
E582211
|
entity |
| Predicate | GND ID |
P26133
|
FINISHED |
| Object | 118503991 |
—
|
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: 118503991 | Statement: [William Bruce Bailey, GND ID, 118503991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GND ID Context triple: [William Bruce Bailey, GND ID, 118503991]
-
A.
GNDID
chosen
Indicates a standardized authority identifier linking an entity to its unique record in the Gemeinsame Normdatei (GND) authority file.
-
B.
gvpId
Indicates a unique identifier assigned to a specific instance of the given predicate or relation within a graph or dataset.
-
C.
GNISID
Indicates that an entity is associated with a specific identifier from the U.S. Geographic Names Information System (GNIS), uniquely linking it to an official geographic feature record.
-
D.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
E.
identifiedIn
Indicates that an entity is recognized, discovered, or documented within a specified source, context, or location.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b02c265c819094728220d77172c6 |
completed | April 29, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:39 p.m.