Triple
T3549010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NTT 3.58 m Telescope |
E75064
|
entity |
| Predicate | hasMirrorSupportSystem |
P50519
|
FINISHED |
| Object | active optics actuators |
—
|
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: active optics actuators | Statement: [NTT 3.58 m Telescope, hasMirrorSupportSystem, active optics actuators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMirrorSupportSystem Context triple: [NTT 3.58 m Telescope, hasMirrorSupportSystem, active optics actuators]
-
A.
hasRepositoryMirror
Indicates that one repository serves as a mirrored copy or synchronized duplicate of another repository.
-
B.
hasSecondaryMirrorPosition
Indicates the spatial placement or configuration of a secondary mirror relative to the primary optical system.
-
C.
mirrorType
Indicates that one entity is a specific kind or category of mirror in relation to another entity.
-
D.
mirrorTechnology
Indicates a relationship where one technology closely reflects, imitates, or duplicates the functionality or design of another.
-
E.
primaryMirrorConfiguration
Indicates the specific structural and optical setup used for a system’s primary mirror.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfd278348190ad2fa54f4a423541 |
completed | March 8, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adba25c66c81909a05a97327828c41 |
completed | March 8, 2026, 6:04 p.m. |
Created at: March 8, 2026, 3:20 p.m.