Triple
T34956118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | vi |
E1008125
|
entity |
| Predicate | defaultEditorOn |
P12001
|
FINISHED |
| Object | many traditional Unix systems |
—
|
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: many traditional Unix systems | Statement: [vi, defaultEditorOn, many traditional Unix systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultEditorOn Context triple: [vi, defaultEditorOn, many traditional Unix systems]
-
A.
defaultEditorSince
Indicates the point in time since which a particular entity has been designated as the default editor for another entity or context.
-
B.
intendedEditor
Indicates that one entity is designated or expected to act as the editor of another entity (such as a document, work, or content).
-
C.
mainEditor
Indicates that one entity serves as the primary editor responsible for overseeing and managing the editing of another entity.
-
D.
earlyEditor
Indicates that an entity served as an editor of another entity at an early stage in its development or production.
-
E.
hasDefaultTextEditor
chosen
Indicates that one entity is designated as the standard or primary text editor used by another entity.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4 p.m.