Triple
T32212861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3D-HST survey |
E822853
|
entity |
| Predicate | proposalId |
P171440
|
FINISHED |
| Object | GO-12177 |
—
|
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: GO-12177 | Statement: [3D-HST survey, proposalId, GO-12177]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposalId Context triple: [3D-HST survey, proposalId, GO-12177]
-
A.
proposalType
Indicates the specific category or kind of proposal associated with an entity or event.
-
B.
proposalNumber
chosen
Indicates that an entity is associated with a specific proposal identified by a unique number.
-
C.
proposalProcess
Indicates the process or sequence of actions involved in creating, submitting, reviewing, and deciding on a proposal between entities.
-
D.
proposalPath
Indicates the sequence or route that a proposal follows through stages, locations, or entities in a process.
-
E.
notableProposal
Indicates that an entity is a proposal distinguished by particular significance, impact, or recognition compared to other proposals.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: May 1, 2026, 12:37 a.m.