Triple
T15387490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESO long-term programme |
E367952
|
entity |
| Predicate | proposalSubmission |
P38599
|
FINISHED |
| Object | ESO observing periods call for proposals |
—
|
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: ESO observing periods call for proposals | Statement: [ESO long-term programme, proposalSubmission, ESO observing periods call for proposals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposalSubmission Context triple: [ESO long-term programme, proposalSubmission, ESO observing periods call for proposals]
-
A.
proposalProcess
Indicates the process or sequence of actions involved in creating, submitting, reviewing, and deciding on a proposal between entities.
-
B.
proposalType
Indicates the specific category or kind of proposal associated with an entity or event.
-
C.
proposalPath
Indicates the sequence or route that a proposal follows through stages, locations, or entities in a process.
-
D.
submissionBy
chosen
Indicates that one entity is the submitter or originator of a particular submission associated with another entity.
-
E.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e761b688190893a81246b735b76 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.