Triple
T44372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William T. Golden |
E870
|
entity |
| Predicate | advisedOn |
P488
|
FINISHED |
| Object | U.S. science and technology policy |
—
|
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: U.S. science and technology policy | Statement: [William T. Golden, advisedOn, U.S. science and technology policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advisedOn Context triple: [William T. Golden, advisedOn, U.S. science and technology policy]
-
A.
advises
chosen
Indicates that one entity provides guidance, recommendations, or counsel to another entity.
-
B.
advisoryProcess
Indicates a relationship where one party provides guidance, recommendations, or expert advice to another through a structured consultative process.
-
C.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
D.
announcedAt
Indicates that an announcement or declaration was made at a specific time or event.
-
E.
confirmedBy
Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
- 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24ba7016481909d595402712db6e2 |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24abbd32c81908cec461d9097662e |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.