Triple
T3062199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Openwater |
E62019
|
entity |
| Predicate | technologyApproach |
P480
|
FINISHED |
| Object | optical imaging |
—
|
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: optical imaging | Statement: [Openwater, technologyApproach, optical imaging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyApproach Context triple: [Openwater, technologyApproach, optical imaging]
-
A.
technologyUse
Indicates the use or application of a particular technology by an entity to perform an action or achieve a purpose.
-
B.
technologyBasis
Indicates that one entity is founded on, enabled by, or fundamentally relies upon the technology provided or represented by another entity.
-
C.
technologyParadigm
chosen
Indicates a relationship where one entity represents or defines the overarching technological model, framework, or approach within which another entity operates or is categorized.
-
D.
technologyTrend
Indicates a relationship where a technology is characterized as part of a broader pattern of change or direction in technological development over time.
-
E.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9e9f33d88190bd481cb7f18ceb91 |
completed | March 8, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69ad962326e081909d5521c3d3ea3158 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.