Triple
T27053375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Datapoint 2200 |
E684837
|
entity |
| Predicate | mainUseCase |
P161803
|
FINISHED |
| Object | remote terminal access |
—
|
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: remote terminal access | Statement: [Datapoint 2200, mainUseCase, remote terminal access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainUseCase Context triple: [Datapoint 2200, mainUseCase, remote terminal access]
-
A.
mainUseCase
chosen
Indicates the primary purpose or most common scenario in which something is intended to be used.
-
B.
mainCase
Indicates that one case is the primary or central case associated with an entity or context, distinguishing it from other related cases.
-
C.
mainFunctions
Indicates that the subject serves as the primary or central functional component or role for the object.
-
D.
mainUseContinued
Indicates that the primary use or function of something persists or remains in effect over a subsequent period.
-
E.
mainSingle
Indicates that an entity is the primary or sole main instance among a set of related entities.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f622b145848190b67cfdc47da6a887 |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:15 a.m.