Triple
T31054024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Systems Consortium website |
E791345
|
entity |
| Predicate | providesDocumentationFor |
P132738
|
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, providesDocumentationFor, BIND]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesDocumentationFor Context triple: [Internet Systems Consortium website, providesDocumentationFor, BIND]
-
A.
documentedUsing
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
-
B.
documentationAvailableIn
Indicates that documentation for an entity is available in a specified medium, format, or location.
-
C.
documentationShownIn
Indicates that certain documentation is displayed or made visible within a particular context, interface, or location.
-
D.
documentationReference
chosen
Indicates that one entity serves as a documentation source or reference that explains, specifies, or supports another entity.
-
E.
documentedThrough
Indicates that something is recorded, evidenced, or made known by means of a specific document or documentation process.
- 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_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 29, 2026, 9 p.m.