Triple
T3549037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HARPS spectrograph |
E75065
|
entity |
| Predicate | usesOpticalFibers |
P11429
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [HARPS spectrograph, usesOpticalFibers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesOpticalFibers Context triple: [HARPS spectrograph, usesOpticalFibers, yes]
-
A.
usesOpticsType
Indicates that one entity employs or is characterized by a specific type of optical system or technology.
-
B.
isTypicallyWiredUsing
chosen
Indicates that one thing is commonly connected or implemented using a particular type of wiring or cabling.
-
C.
opticalProperty
Indicates a relationship where an entity has or is characterized by a specific optical property, such as how it interacts with or responds to light.
-
D.
opticalDesign
Indicates a relationship where one entity is responsible for creating, specifying, or defining the optical configuration or characteristics of another entity.
-
E.
requiresModeConditioningPatchCordOnMultimode
Indicates that a mode-conditioning patch cord must be used when connecting to or operating over multimode fiber.
- 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_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. |
Created at: March 8, 2026, 3:20 p.m.