Triple
T28609068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EncFS |
E724126
|
entity |
| Predicate | originalHostingPlatform |
P61964
|
FINISHED |
| Object | SourceForge |
—
|
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: SourceForge | Statement: [EncFS, originalHostingPlatform, SourceForge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalHostingPlatform Context triple: [EncFS, originalHostingPlatform, SourceForge]
-
A.
originPlatform
chosen
Indicates the platform, system, or environment from which an entity, event, or piece of data originally comes.
-
B.
hostedOn
Indicates that one entity operates, resides, or is made available on another entity that provides the underlying platform or infrastructure.
-
C.
originalHost
Indicates that one entity is the initial or primary host on which another entity first resided, originated, or was hosted.
-
D.
hostedFrom
Indicates that something (such as a service, application, or event) is provided, run, or made available starting from a particular location, source, or environment.
-
E.
originalWebsite
Indicates that one entity is the original or primary website from which another entity (such as a copy, mirror, or derivative site) is derived.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: April 28, 2026, 4:29 a.m.