Triple
T28114266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ClearSight |
E710576
|
entity |
| Predicate | dataAcquisitionSite |
P80199
|
FINISHED |
| Object | finger |
—
|
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: finger | Statement: [ClearSight, dataAcquisitionSite, finger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataAcquisitionSite Context triple: [ClearSight, dataAcquisitionSite, finger]
-
A.
dataAcquisition
Indicates the process by which one entity obtains, collects, or retrieves data from another source or system.
-
B.
developmentSiteOf
Indicates that a particular site or location is the place where a specified development project or construction activity occurs or is planned to occur.
-
C.
dataCollectionLocation
chosen
Indicates the place or setting where data is gathered, recorded, or measured.
-
D.
mainDiscoverySite
Indicates the primary location where something (such as an object, specimen, or phenomenon) was originally discovered.
-
E.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
- 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f640ca4480819089a6b9fd78c45ab2 |
completed | May 2, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:13 p.m.