Triple
T26518821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VLT instrumentation suite |
E669894
|
entity |
| Predicate | enablesObservationType |
P42123
|
FINISHED |
| Object | interferometry |
—
|
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: interferometry | Statement: [VLT instrumentation suite, enablesObservationType, interferometry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesObservationType Context triple: [VLT instrumentation suite, enablesObservationType, interferometry]
-
A.
supportsObservationModes
chosen
Indicates that one entity provides or is compatible with specific modes or methods of observation used by another entity.
-
B.
observesType
Indicates that one entity observes, monitors, or takes note of another entity of a specified type.
-
C.
supportsObservation
Indicates that one entity provides evidence, context, or infrastructure that enables or strengthens the validity of an observation made about another entity.
-
D.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
E.
hasObservationTargetType
Indicates that an observation is directed toward or concerns a specific type or category of target.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 1:26 a.m.