Triple
T19352160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerald Combs |
E484048
|
entity |
| Predicate | softwareEngineeringDiscipline |
P37802
|
FINISHED |
| Object | network software |
—
|
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: network software | Statement: [Gerald Combs, softwareEngineeringDiscipline, network software]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareEngineeringDiscipline Context triple: [Gerald Combs, softwareEngineeringDiscipline, network software]
-
A.
softwareDomain
chosen
Indicates that something belongs to, operates within, or is associated with a particular area or field of software.
-
B.
programmingEvolution
Indicates how programming practices, languages, or paradigms change and develop over time.
-
C.
programming
Indicates that an entity writes, develops, or modifies software or code, typically using a programming language to create or control computer programs.
-
D.
engineeringStandard
Indicates that something conforms to, is defined by, or is governed by a specified engineering standard or set of technical norms.
-
E.
treatsProgrammingAs
Indicates viewing or regarding programming in a particular way, such as as a hobby, a job, an art, or a tool.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61905b16881909ab0e932bb9a0cda |
completed | April 20, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e4dd13a8cc81909cd02668564c9f29 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.