Triple
T33027473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PASV |
E845079
|
entity |
| Predicate | commonlySupportedBy |
P3697
|
FINISHED |
| Object | FTP clients |
—
|
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 clients | Statement: [PASV, commonlySupportedBy, FTP clients]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlySupportedBy Context triple: [PASV, commonlySupportedBy, FTP clients]
-
A.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
B.
isSupportedBy
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
-
C.
commonlyImplementedBy
chosen
Indicates that the referenced item (e.g., a standard, interface, or pattern) is frequently realized or put into practice by the associated implementing entities.
-
D.
firstSupportedBy
Indicates that an entity is initially upheld, enabled, or made possible by another entity that provides its primary support.
-
E.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 1, 2026, 1:23 a.m.