Triple
T32257226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Deep Field |
E824056
|
entity |
| Predicate | proposalLedBy |
P180558
|
FINISHED |
| Object | Robert Williams |
—
|
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: Robert Williams | Statement: [Hubble Deep Field, proposalLedBy, Robert Williams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposalLedBy Context triple: [Hubble Deep Field, proposalLedBy, Robert Williams]
-
A.
proposalSolicitedBy
Indicates that a proposal was requested or invited by a particular party or entity.
-
B.
proposalType
Indicates the specific category or kind of proposal associated with an entity or event.
-
C.
proposalNumber
Indicates that an entity is associated with a specific proposal identified by a unique number.
-
D.
proposalProcess
Indicates the process or sequence of actions involved in creating, submitting, reviewing, and deciding on a proposal between entities.
-
E.
coProposedBy
Indicates that a proposal, idea, or item is jointly put forward or suggested by multiple entities together.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: May 1, 2026, 12:41 a.m.