Triple
T36096419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurs |
E1044073
|
entity |
| Predicate | backupBy |
P165207
|
FINISHED |
| Object | TORU manual docking system |
—
|
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: TORU manual docking system | Statement: [Kurs, backupBy, TORU manual docking system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backupBy Context triple: [Kurs, backupBy, TORU manual docking system]
-
A.
backupFeatureIn
chosen
Indicates that one feature serves as a backup or fallback for another feature within a given context or system.
-
B.
backsUp
Indicates that one entity provides support, reinforcement, or confirmation for another entity’s actions, statements, or position.
-
C.
backupCommander
Indicates that one entity serves as the designated backup or alternate commander for another entity.
-
D.
supportsBackupCopy
Indicates that one entity provides the capability or functionality to create, maintain, or use a backup copy of another entity.
-
E.
backupScope
Indicates the extent or range of data, resources, or components that are included in a backup operation.
- 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.