Triple
T9515384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gopher |
E229510
|
entity |
| Predicate | URLScheme |
P60776
|
FINISHED |
| Object | gopher:// |
—
|
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: gopher:// | Statement: [Gopher, URLScheme, gopher://]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: URLScheme Context triple: [Gopher, URLScheme, gopher://]
-
A.
hasScheme
Indicates that one entity is associated with, defined by, or governed through a particular scheme, plan, or structured framework.
-
B.
URLPattern
Indicates that a resource or endpoint is identified or matched by a specific structured web address pattern.
-
C.
targetProtocol
chosen
Indicates the communication protocol that an action, message, or connection is intended to use or be directed toward.
-
D.
accessURL
Indicates the web address or endpoint through which a resource can be accessed or retrieved.
-
E.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd986d5af08190a001c5a5ff647d4d |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:58 p.m.