Triple
T29873851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mod_http2 |
E758665
|
entity |
| Predicate | partOfSoftware |
P840
|
FINISHED |
| Object | Apache HTTP Server |
—
|
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: Apache HTTP Server | Statement: [mod_http2, partOfSoftware, Apache HTTP Server]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfSoftware Context triple: [mod_http2, partOfSoftware, Apache HTTP Server]
-
A.
partOfSystem
chosen
Indicates that one entity functions as a component or subsystem within the structure or organization of another entity.
-
B.
isPartOfFramework
Indicates that one entity functions as a component, module, or element within a larger structured framework or system.
-
C.
implementedAsPartOf
Indicates that something has been realized or carried out as a component or subset of a larger implementation or project.
-
D.
softwareSystem
Indicates a relationship where an entity functions as, or is classified as, a software system.
-
E.
developedAsPartOf
Indicates that something was created, produced, or evolved as a component or subset of a larger project, system, or initiative.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
Created at: April 29, 2026, 5:54 p.m.