Triple
T21983166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebBrowser |
E542891
|
entity |
| Predicate | maySupportProtocol |
P35980
|
FINISHED |
| Object | FTP |
—
|
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: FTP | Statement: [WebBrowser, maySupportProtocol, FTP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maySupportProtocol Context triple: [WebBrowser, maySupportProtocol, FTP]
-
A.
supportedProtocol
chosen
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
B.
mayHaveSupported
Indicates that an entity possibly provided assistance, endorsement, or backing to another entity, without asserting that this support definitely occurred.
-
C.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
-
D.
alsoSupports
Indicates that an entity, in addition to its primary or previously stated function, provides support for another entity, feature, or activity.
-
E.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1270629588190aea32fbe630e4cba |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:04 p.m.