Triple
T31054026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Systems Consortium website |
E791345
|
entity |
| Predicate | providesDownloadsFor |
P79779
|
FINISHED |
| Object | BIND |
—
|
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: BIND | Statement: [Internet Systems Consortium website, providesDownloadsFor, BIND]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesDownloadsFor Context triple: [Internet Systems Consortium website, providesDownloadsFor, BIND]
-
A.
providesDirectLinkTo
Indicates a relationship where one entity offers an immediate, non-intermediated connection or access path directly to another entity.
-
B.
downloadFrom
Indicates that a file, data, or resource is transferred and obtained from a specified source or provider.
-
C.
supportsDigitalDownloads
chosen
Indicates that one entity enables or allows the other entity to provide or access digital file downloads.
-
D.
toolkitDownloadURL
Indicates the web address from which a specific toolkit can be downloaded.
-
E.
providesThat
Indicates that one entity stipulates, specifies, or sets forth a condition, rule, or provision that applies to another entity or situation.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: April 29, 2026, 9 p.m.