Triple
T9712743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GhostBSD |
E235058
|
entity |
| Predicate | downloadFrom |
P90390
|
FINISHED |
| Object | official GhostBSD website |
—
|
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: official GhostBSD website | Statement: [GhostBSD, downloadFrom, official GhostBSD website]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: downloadFrom Context triple: [GhostBSD, downloadFrom, official GhostBSD website]
-
A.
toolkitDownloadURL
Indicates the web address from which a specific toolkit can be downloaded.
-
B.
downstreamFrom
Indicates that one entity is located or occurs at a point further along the natural flow or direction of another entity, typically in a linear or directional system such as a river, pipeline, or process sequence.
-
C.
draftFrom
Indicates that one item is created, written, or formulated based on or derived from another source or version.
-
D.
down
Indicates that one entity is located at a lower position or level relative to another entity or reference point.
-
E.
distributionHub
Indicates a location or facility that serves as a central point for receiving, sorting, and redistributing goods or resources to multiple destinations.
- F. None of above. chosen
Provenance (4 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e0705f8819095852263009c28c5 |
completed | April 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:19 p.m.