Triple
T2988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Las Campanas Observatory |
E55
|
entity |
| Predicate | openTo |
P273
|
FINISHED |
| Object | professional astronomers |
—
|
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: professional astronomers | Statement: [Las Campanas Observatory, openTo, professional astronomers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openTo Context triple: [Las Campanas Observatory, openTo, professional astronomers]
-
A.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
B.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
C.
grantedTo
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
-
D.
submittedTo
Indicates that one entity has formally sent or presented something (such as a document, request, or work) to another entity for consideration, review, or processing.
-
E.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
- 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_69a2328f0e848190ac2840eaf2d5ebd2 |
completed | Feb. 28, 2026, 12:10 a.m. |
| NER | Named-entity recognition | batch_69a2346846608190b6b40d31f1dbd685 |
completed | Feb. 28, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69a233c396ec8190986608d07fb251d4 |
completed | Feb. 28, 2026, 12:16 a.m. |
Created at: Feb. 28, 2026, 12:13 a.m.