Triple
T30420492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas E. Dickey |
E773890
|
entity |
| Predicate | softwareProjectMaintainerOf |
P11213
|
FINISHED |
| Object | xterm |
—
|
NE NERFINISHED |
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: xterm | Statement: [Thomas E. Dickey, softwareProjectMaintainerOf, xterm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareProjectMaintainerOf Context triple: [Thomas E. Dickey, softwareProjectMaintainerOf, xterm]
-
A.
developmentProject
Indicates a relationship where an organized effort or initiative is undertaken to plan, create, improve, or expand something over a defined period.
-
B.
softwareTypeMaintained
Indicates that an entity is responsible for maintaining or supporting a particular type of software.
-
C.
overseesProject
chosen
Indicates that one entity has responsibility for supervising, managing, or directing the progress and execution of a project involving another entity.
-
D.
managementSoftware
Indicates that one entity is a software system used to organize, control, or coordinate the operations, resources, or processes of another entity.
-
E.
softwareSystem
Indicates a relationship where an entity functions as, or is classified as, a software system.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:05 p.m.